-
Notifications
You must be signed in to change notification settings - Fork 417
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
Copy symlinked module and transpile symlinked Typescript files #963
Labels
awaiting reply
Awaiting for a reply from the OP
Comments
@zirkelc If I am reading this correctly, this sounds like a |
@zirkelc I've been dealing with the exact same problem you had for a couple of days now. Do you happen to remember how you got it fixed? |
I stopped using Lerna for local dependencies and I switched over to serverless-esbuild. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a Bug
Description
I'm using Lerna to add a local package @abc/foundation as dependency to my other package @abc/connector. Lerna creates a symlink inside
./connector/node_modules
which links to../foundation/
. In webpack.config.js I useexternals: [nodeExternals()
to copy all node_modules to .webpack to avoid the issues with npm install (#580 (comment)).sls package
then throws the following error:It seems like the symlink is broken when it is copied to the .webpack folder. I looks like the symlink is referencing itself.
I tried to change the webpack externals to allow my project name
externals: [nodeExternals({ allowlist: [/^@abc/] })
as recommended in this issue #201 (comment)This will end up in a webpack compilation error as webpack has no loader configured to transpiled Typescript files inside nodule_modules folder:
webpack.config.js
Similar or dependent issue(s):
Additional Data
The text was updated successfully, but these errors were encountered: