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

Update iconv-lite to latest 0.6.3 #476

Open
jperelli opened this issue Nov 30, 2022 · 7 comments
Open

Update iconv-lite to latest 0.6.3 #476

jperelli opened this issue Nov 30, 2022 · 7 comments
Labels

Comments

@jperelli
Copy link

In a project I work we use body-parser and mysql2 as dependencies.
We are running a very common combination of prisma+mysql2 / expressjs+bodyparser in vercel, and every bundle kb is important in cold start lambda functions.

mysql2 depends on iconv-lite: 0.6.3 and body-parser depends on iconv-lite: 0.4.24

I think it can be upgraded in body-parser to have the same library and avoid code duplication. This would save around 600kb (~500kb of duplication + ~100kb of improved bundle size in 0.6.0).

Thank you for this great project!

@dougwilson
Copy link
Contributor

Hello, and sorry for the delay on responding; I didn't realize I never did. I took a look and it seems that there are some breaking changes in that upgrade path. I will, however, work to get it fully upgraded in our 2.0 branch 👍

@dougwilson dougwilson added the deps label Feb 5, 2023
@RahulGautamSingh
Copy link

RahulGautamSingh commented Jun 19, 2023

Maybe using a automatic dependency bot like: renovate or dependabot can be useful?
As the automated PRs will make it easier to see the errors/problems that might come with new updates and making the issues visible for contributors💪
I would be happy to set them up if that's okay.☺

@dougwilson
Copy link
Contributor

Hi @RahulGautamSingh I'm not sure how that would help here, as it is not upgraded in 1.x because it has breaking changes that requires a major version bump for body-parser.

@RahulGautamSingh
Copy link

Regular update PRs will help keep all deps up-to-date, and if some dep-updates require version bump then those can be targeted to the branch which is under work ie. 2.0 branch.

@dougwilson
Copy link
Contributor

dougwilson commented Jun 19, 2023

Thanks, but I don't think having that is necessary; I already use a service that shows all ourdated on a central dashboard.

@RahulGautamSingh
Copy link

RahulGautamSingh commented Jun 19, 2023

No problem! I thought I should comment once as you mentioned that you forgot to upgrade the dep and automated PRs will be handy there. ✌

Thanks for all the work you have put in making and maintaining project, it really help a lot!♥

@dougwilson
Copy link
Contributor

dougwilson commented Jun 19, 2023

Sorry, I meant I forgot to reply to this issue; not that I forgot to update the dep. I already knew it was out of date but incompatible.

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

No branches or pull requests

3 participants