Workaround for failed imports?

[jelleag]

I am currently running into a variant of a known issue: ESM imports escape the runfiles tree and the sandbox due to #362.

[vite]: Rollup failed to resolve import "@emotion/cache" from "../../../../../../../../node_modules/.aspect_rules_js/@[email protected]_sogmqz4enknxtkxk3k5s6bqwnq/node_modules/@mantine/styles/esm/index.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`

One workaround seems to be running the Vite binary from the root, but this is undesirable as I'm working with a monorepo. Are there currently any other workarounds, or maybe a timeline for the fix?

Many thanks in advance!

[gregmagolan]

#362 is a tricky one. Its a small change in the node source code that would fix it but the internal .js file that needs the change is compiled into the node binary so it would mean forking node and building it from source.

Your problem above however looks more like a pnpm strict dependency issue to me.

It looks like @mantine/styles doesn't declare a dep on @emotion/cache: https://unpkg.com/@mantine/[email protected]/package.json

You can inject the missing dependency with pnpm packageExtensions however. For example, we inject mocha-multi-reporters as a peer dep of mocha here:

rules_js/package.json

Line 12 in d1cb223

"mocha-multi-reporters": "*"

See https://pnpm.io/package_json#pnpmpackageextensions for more info

[jelleag]

@gregmagolan Greg, you are a hero. Have been struggling with this for so long. Your workaround works like a charm!

[gregmagolan]

Awesome.

BTW, I tried out the change in Node.js that is needed to fix #362 and verified that it does work as expected. #362 (comment). Next step is to get it landed in node.