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

Upgrade dependencies #374

Closed
gligorkot opened this issue Aug 30, 2024 · 4 comments · Fixed by #375
Closed

Upgrade dependencies #374

gligorkot opened this issue Aug 30, 2024 · 4 comments · Fixed by #375

Comments

@gligorkot
Copy link
Contributor

Some of the dependencies within this package are marked with critical and high security issues. We should upgrade the dependencies to eliminate these.

@henhal
Copy link

henhal commented Aug 30, 2024

Also struggling to catch up with audit warnings today and serverless-bundle is really making it difficult for me. This package basically isn't updated in years it seems. Is it abandoned?

@gligorkot
Copy link
Contributor Author

@henhal feel free to use my fork which is PR #375, it has eliminated all of the vulnerable dependencies here.

@henhal
Copy link

henhal commented Aug 30, 2024

That's awesome @gligorkot. Pending that PR being managed and a new official release to be made, are you considering making a npm release from your fork so we can use npm install @gligorkot/serverless-bundle, or should we use git+ssh syntax?

@gligorkot
Copy link
Contributor Author

@henhal I only raised it today, so I'm hoping @jayair or someone from the SST team to help merge it in soon. Last PR I added here got merged within a day or two, I'm hoping it'll be similar again.

So I'd say if you need it urgently, go with the git+ssh for now until we hear back from the maintainers. No plan to push my own version at the moment, unless the maintainers have decided to stop maintaining this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants