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
Currently the runtime dependencies appear in the top-level ./package.json and ./dependencies/nodejs/package.json. The former for IDE's to index for code completion and the latter for specifying what's uploaded as a lambda layer. It would be nice to remove this duplication. Symbolic links might be useable to avoid duplicates of the runtime dependencies in both node_modules. That would still leave duplicates in the package.json and package.lock, whose versions could potentially go out of sync. That's rubbish.
solve the duplication issue above
update the README with the procedure for adding new runtime dependencies
The text was updated successfully, but these errors were encountered:
Currently the runtime dependencies appear in the top-level
./package.json
and./dependencies/nodejs/package.json
. The former for IDE's to index for code completion and the latter for specifying what's uploaded as a lambda layer. It would be nice to remove this duplication. Symbolic links might be useable to avoid duplicates of the runtime dependencies in bothnode_modules
. That would still leave duplicates in thepackage.json
andpackage.lock
, whose versions could potentially go out of sync. That's rubbish.The text was updated successfully, but these errors were encountered: