Running with expo canary

[stephenhandley]

Describe the issue

I've been trying to get react-strict-dom working with expo@canary and running into Uncaught TypeError: _interopRequireDefault is not a function.

Expected behavior

Hoping to be able to use react-strict-dom with Expo latest to port a web ui library which uses React 19 to work with Expo

Steps to reproduce

Here is a repo with the process I used and should be cloneable to quickly repro:
https://github.com/stephenhandley/expo-rsd

As described there, I followed the process described here follow by the process in your docs

Test case

https://github.com/stephenhandley/expo-rsd

Additional comments

No response

[necolas]

This is the stack trace:

Uncaught TypeError: _interopRequireDefault is not a function
    at HMRClient.ts:11:1
    at loadModuleImplementation (require.js:277:5)
    at guardedLoadModule (require.js:184:12)
    at metroRequire (require.js:92:7)
    at setupHMR.ts:1:1
    at loadModuleImplementation (require.js:277:5)
    at guardedLoadModule (require.js:184:12)
    at metroRequire (require.js:92:7)
    at effects.ts:8:5
    at loadModuleImplementation (require.js:277:5)

Your example doesn't even import RSD in any files that get bundled. I don't see anything pointing to RSD being the issue.

[stephenhandley]

The README.md on that repo describes things in more detail, maybe should have put it in this ticket.

Things work fine going through the canary setup until I follow the install process you're describing in your docs. The postcss and babel configs work fine but the metro.config.js causes the above error, this line in particular when uncommented, results in error/stacktrace I shared.

config.resolver.unstable_enablePackageExports = true;

I tried workarounds importing RSD components without that enabled but had no luck. Let me know if you would like more details there.

Here's the commit right before doing install process where things render fine with expo canary.
stephenhandley/expo-rsd@ad3ce6f

Can you suggest any workarounds for the metro config?

[necolas]

The README.md on that repo describes things in more detail, maybe should have put it in this ticket.

Yeah that would be a good idea. But thanks, that README explains the issue better.

I then get the following error

Web Bundling failed 2384ms index.js (326 modules)
 ERROR  stylex.css: ~/expo-rsd/node_modules/postcss-react-strict-dom/src/index.ts: `export = <value>;` is only supported when compiling modules to CommonJS.
Please consider using `export default <value>;`, or add @babel/plugin-transform-modules-commonjs to your Babel config.
  115 | plugin.postcss = true
  116 |
> 117 | export = plugin
      | ^^^^^^^^^^^^^^^
  118 |
› Detected a change in babel.config.js. Restart the server to see the new results. You may need to clear the bundler cache with the --clear flag for your changes to take effect.

@javascripter looks like the exports in the postcss plugin are a problem. Maybe we should move that plugin to this repo, so it's easier for us to keep up to date and patch.

If I comment out this line on metro.config.js the app will render, but then unsurprisingly can't import react-strict-dom components: config.resolver.unstable_enablePackageExports = true

Hmm, it's possible there's a regression in the Expo canary, if Metro changed. Let's see if @EvanBacon has any ideas. I'm not sure where Expo/Metro stands on support for package exports these days.

[javascripter]

@necolas

@javascripter looks like the exports in the postcss plugin are a problem. Maybe we should move that plugin to this repo, so it's easier for us to keep up to date and patch.

Yes, I don't mind moving the code over here.
Currently, StyleX's official PostCSS Plugin basically mirrors my postcss-react-strict-dom repo with typescript code stripped out.

I see two options to proceed:

1. I think you could simply re-export @stylexjs/postcss-plugin with default include merged under packages/react-strict-dom/postcss-plugin or packages/postcss-plugin.
2. Or simply copy-paste from StyleX repo and maintain it here directly.

I think 1 is easier to maintain for now. Do you want me to create a PR or you can handle that yourself?

[lundn]

I'm not sure if this is the case, but I suspect the error you're experiencing is related to the glob pattern used in your postcss.config.js. Both your application code and e.g config files exists on the same level. This mean all .js files (config files included) will be a part of the postcss processing.

Could you try to either move application code inside a top-level src folder or be more specific in the include / exlude options?

[necolas]

@javascripter PR for your suggestion would be appreciated if you have time. Thanks!

@lundn I had the same thought

[stephenhandley]

@lundn thanks for the suggestion, had tried that previously with no luck wrt to the interopRequireDefault error.
https://github.com/stephenhandley/expo-rsd/pull/2/files

However, went through the setup process again with a src dir and it does avoid the initial postcss export = plugin error. It didn't require installing @babel/plugin-transform-modules-commonjs.

Have cleaned things up to remove usage of that from the repro, also added the react-strict-dom import to demonstrate the error when unstable_enablePackageExports is off:

Web Bundling failed 1176ms src/index.js (324 modules)
Unable to resolve "react-strict-dom/runtime" from "src/App.js"

[javascripter]

@necolas
Sent a PR to move the plugin to this repo.

[lundn]

@stephenhandley @necolas I'm setting up a new monorepo with an Expo app (latest) in order to ask for help on another issue with RSD / StyleX / PostCSS. I quickly experienced the same issue as @stephenhandley has regarding config.resolver.unstable_enablePackageExports = true; resulting in Uncaught TypeError: _interopRequireDefault is not a function.

By chance I found an thread on Expo's discord mentioning that unstable_conditionNames seemed to fix a relating issue. I've not investigated why or how, but setting config.resolver.unstable_conditionNames = ["require", "default", "browser"]; in conjunction with unstable_enablePackageExports seems to fix the issue.

Do you have any thoughts (even though I understand this might not directly be a RSD issue)?

[necolas]

My thoughts are that I wish Metro and Expo actually worked properly with modern packaging practices. Or at least documented what to do / stopped breaking frequently when people upgrade

[stephenhandley]

@lundn nice find, thank you! can verify this resolves the issue on my end.

I had missed that in the Metro documentation previously, but seeing now that it is mentioned here along with another experimental unstable_conditionsByPlatform flag:
https://metrobundler.dev/docs/configuration/#unstable_conditionnames-experimental
https://metrobundler.dev/docs/configuration/#unstable_conditionsbyplatform-experimental

[stephenhandley]

Still needs a lot of cleanup but have gotten the basics of things working with Expo+Next and a shared ui lib in a monorepo here:
https://github.com/stephenhandley/expo-rsd