Doesn't upgrading next to latest ( 15.3.2 ) resolve babel vulnerability, why does it still show?
Unanswered
Australian Freshwater Crocodile posted this in #help-forum
Australian Freshwater CrocodileOP
I've been trying to resolve this vulnerability for a while ow and can seem to get it done.
Ive tried upgrading next, and overriding babel in package.json to 7.26.10. However, it still seems to show the vulnerability is not resolved.
Ive tried upgrading next, and overriding babel in package.json to 7.26.10. However, it still seems to show the vulnerability is not resolved.
2 Replies
Australian Freshwater CrocodileOP
I see the correct version in the standalone build but the incorrect version still persists
Australian Freshwater CrocodileOP
I ended up just reconfiguring my app for a standalone app, as a way to not include nextjs in build. Though I would till like to know how the old babel version is being kept even though the new latest version of nexts uses a newer one.