-
-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@module-federation/node __dirname #1467
Comments
are you trying to read from the hosts local directory? via a remote? Can you try the latest prerelease on npm, under the "next" tag |
Ive found the problem, looks related to something in the node plugin targeting system (i think) #1268 solves it (i just encountered this and fixed) but its attached to a much larger PR which isnt releasing yet. |
If I understand correctly, I need to wait for the merge :) For information. Maybe you will be interested Or git hub links I convert build to TypeScript, and clear extra @babel library.
Formally, there are two problems left:
Thank you |
You can do dynamic loading on server: https://github.com/module-federation/module-federation-examples/tree/master/dynamic-remotes-node My utilities work univerally as they all use low level webpack runtime apis, so we hook into the same thing webpack statically does at compile. Ill need to verify it still works as expected with the new rewrites in that PR youre waiting on. I may publish a new pre-release to npm today so just look out for "next" tag on the package you want on npm and there should ne a new update soon |
For version ^2.0.2-beta.3 don't have npm https://www.npmjs.com/package/@swc/helpers
|
After install package @swc/helpers. for both project, I have new exception for version 2.0.2-beta.3
external {} |
Thank you. I try use injectScript for configuration:
but I have an exception because the library search for the file "Logger.js" inside my source folder and not inside the package.
|
ive release newer prereelases that my help with this now, my CI has some issues and caused bad released to go out |
Hi.
I have two problems with __dirname, for @module-federation/node version 1.0.7.
Me need to __dirname for express:
The text was updated successfully, but these errors were encountered: