support symlinked packages
See original GitHub issueHello,
it seems like I`m unable to use symlinked packages via lerna. When I start it with sls offline it works. When I try to deploy it always takes the npm - version of my (monorepo) package instead of the local version
This is a Feature Proposal
Description
For feature proposals: detect if a package is symlinked and copy/attach this to the node_modules folder for webpack.
-
If there is additional config how would it look
webpack: includeModules: forceSymlink: - [packagename]
Similar or dependent issue(s):
Additional Data
- Serverless-Webpack Version you’re using: 5.3.1
- Webpack version you’re using:
- Serverless Framework Version you’re using: 1.67.3
- Operating System: Mac OS
- Stack Trace (if available):
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:16 (3 by maintainers)
Top Results From Across the Web
NuGet packaging should support symlinks within ... - GitHub
We create nuget packages on Linux and macOS by 'nuget.exe pack ..'. Our source folder contains libraries and the set of symbolic links...
Read more >Symlinks in Windows 10! - Windows Developer Blog
A symlink is essentially a pointer to a file or folder located elsewhere, consumes little space and is very fast to create (compared...
Read more >npm-link
Symlink a package folder. ... This can be used to work around the fact that some file systems don't support symlinks, even on...
Read more >Symlinked `node_modules` structure - PNPM
pnpm's node_modules layout uses symbolic links to create a nested structure of dependencies. Every file of every package inside node_modules is a hard...
Read more >Ubuntu Manpage: npm-link - Symlink a package folder
First, npm link in a package folder will create a globally-installed symbolic link from prefix/package-name to the current folder (see npm help 7...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@mogusbi-motech @pharindoko I managed to work around the issue by switching to the
file:../package-name
notation in mydependencies
.I did not need to add my symlinked module to
webpack-node-externals
’s whitelist. But I did need to use the following setting inserverless.yml
to get rid of my dependency’s devDependencies which were raising my bundle size way above the 250mb limit:Any workaround or help is appreciated too. I cannot use local symlinked packages added by “lerna add” command.