Open donmccurdy opened 1 year ago
any progress?
@machao7 You can subscribe to the issue and get notified whenever there's progress. When there is, you'd see it here.
Honestly I'd recommend avoiding the browser field spec anyhow, package.json#exports
has completely eclipsed it. Output separate browser & Node bundles, don't rely upon bundlers patching out your imports. It's always been a pretty bad hack for isomorphic modules.
That being said, likely just need to bump @rollup/plugin-node-resolve
, looks to be related to https://github.com/rollup/plugins/issues/1048 & https://github.com/rollup/plugins/pull/1124
Similar to https://github.com/developit/microbundle/issues/989, but now occurring only when Microbundle's target is not Node.js. I'm compiling a library that runs in both Node.js and a browser, and the library contains dynamic imports for node built-ins like 'fs', executed only in Node.js.
When importing
fs
I can add the following to mypackage.json
and everything works fine:However, using
node:fs
, the same thing does not work, and warnings appear with:Microbundle v0.15.1, Node.js v18.12.1.