Skip to content
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

Npm modules are being cleared out when multiple modules are used. #65

Closed
kcthota opened this issue May 15, 2023 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@kcthota
Copy link
Collaborator

kcthota commented May 15, 2023

Create two pipelines and use a different npm module in each pipeline.

Send events to the pipeline.

Pipeline1 will download the required module while processing the event. When Pipeline2's event is being processed, the Pipeline1's downloaded dependency is automatically removed.

@kcthota kcthota self-assigned this May 15, 2023
@kcthota kcthota added the bug Something isn't working label May 15, 2023
@kcthota
Copy link
Collaborator Author

kcthota commented May 15, 2023

Issue seems to be caused by npm/npm#16853.

npm install seems to auto prune causing all modules installed as --no-save to be removed.

kcthota added a commit that referenced this issue May 15, 2023
kcthota added a commit that referenced this issue May 15, 2023
Fixes #65 -  npm install causes install modules to be auto pruned
kcthota added a commit that referenced this issue May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant