Closed ceefour closed 6 years ago
Workaround from @stojanovic :
you can use
--use-local-dependencies
option in Claudia and deploy whatever you have in your localnode_modules
, or simply fork a repo and fix the issue, just install the module from your fork, not from NPM.
@ceefour one of the goals of Claudia is not to introduce too much magic, so we use NPM for package management. local dependencies are the right way to solve it, not a workaround, so I’ll close this issue.
patch-package is very useful for forking/fixing a problem in the meantime before official bugfix.
Expected behaviour: deployed code runs patch-package (i.e.
prepare
script inpackage.json
)What actually happens: claudia npm installs the "pure packages" without running patches, this can be verified by using
claudia --keep
Link to a minimal, executable project that demonstrates the problem: any project with any patch-package patch
Steps to install the project:
claudia create
/claudia update
Steps to reproduce the problem:
npm install --save patch-package
node_modules/aws-serverless-express/express/src/index.js
even adding comment will donpx patch-package aws-serverless-express
claudia create --keep ...