You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to speed up our build process we switched to symlinking the /dist/node_modules folder to our ./node_modules folder instead of copying it over on builds.
Unfortunately this seems to break sam local start-api as on the very first require it cannot find the module.
Is there some way to get this to work or just not supported?
The text was updated successfully, but these errors were encountered:
ktersius
changed the title
Symlinked node_modules breaks sam local start-api
Does sam support sym linked node_modules?
Oct 6, 2019
For symlinks to work inside containers, I believe they need to be absolute paths, and both directories need to be mounted within the container. Need to dig deeper on this particular issue.
Going to close this issue in favor of esbuild solutions for faster builds along with cached and parallel builds. Please re-open this issue if it's still something that we need to target.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
In order to speed up our build process we switched to symlinking the /dist/node_modules folder to our ./node_modules folder instead of copying it over on builds.
Unfortunately this seems to break sam local start-api as on the very first require it cannot find the module.
Is there some way to get this to work or just not supported?
The text was updated successfully, but these errors were encountered: