Skip to content

[Snyk] Upgrade core-js from 3.14.0 to 3.47.0 #116

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.

Sign up for GitHub

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

Jump to bottom
Open
nejidevelops wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade core-js from 3.14.0 to 3.47.0 #116

nejidevelops wants to merge 1 commit into from

Conversation

@nejidevelops
Copy link
Owner

@nejidevelops nejidevelops commented Dec 15, 2025

snyk-top-banner

Snyk has created this PR to upgrade core-js from 3.14.0 to 3.47.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 88 versions ahead of your current version.

  • The recommended version was released a month ago.

Release notes
Package name: core-js from core-js GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

@snyk-bot
fix: upgrade core-js from 3.14.0 to 3.47.0
ab1d34b 
Snyk has created this PR to upgrade core-js from 3.14.0 to 3.47.0.

See this package in npm:
core-js

See this project in Snyk:
https://app.snyk.io/org/newtonombese1/project/a1ad30ab-9c5a-44d9-b1ec-8602e717f1b9?utm_source=github&utm_medium=referral&page=upgrade-pr
@gemini-code-assist
Copy link

gemini-code-assist bot commented Dec 15, 2025

Summary of Changes

Hello @nejidevelops, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, updates the core-js dependency from version 3.14.0 to 3.47.0. This substantial upgrade aims to keep the project's dependencies current, integrating a wide array of new ECMAScript features, polyfills for upcoming proposals, and critical bug fixes, thereby enhancing compatibility and future-proofing the codebase.

Highlights

  • Dependency Upgrade: Upgraded the core-js dependency from version 3.14.0 to 3.47.0, a significant jump of 88 versions, to incorporate numerous new features, bug fixes, and compatibility improvements.
  • New ECMAScript Proposals: The upgrade brings polyfills for several new and evolving ECMAScript proposals, including JSON.parse source text access, Iterator sequencing, Joint iteration, Uint8Array to/from base64/hex, Math.sumPrecise, Map upsert, Explicit Resource Management, Array.fromAsync, Error.isError, RegExp.escape, Float16, and Iterator helpers.
  • Bug Fixes and Compatibility: Includes various bug fixes, such as issues with URLSearchParams.prototype.append in IE8-, Map upsert in Firefox, Iterator.zip and Iterator.zipKeyed behavior, Object.groupBy with Symbol polyfill, Uint8Array.fromHex and setFromBase64 in V8, Iterator.concat behavior, Number.prototype.clamp behavior, and numerous browser compatibility data improvements across different engines (V8, Firefox, Safari, Node.js, Deno, Bun, Electron, Opera, Oculus Quest Browser, Samsung Internet, Rhino).
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Dec 15, 2025
View reviewed changes
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, upgrades core-js from version 3.14.0 to 3.47.0. This is a significant update, spanning 88 releases. While it's not a major version change, I've identified several potentially breaking changes in the release notes that could impact the application. My review comment on package.json details these potential issues and highlights the importance of thorough regression testing before merging. Overall, the upgrade is beneficial for keeping dependencies up-to-date, but it carries a non-trivial risk that needs to be managed through testing.

vue-app/package.json
"axios": "^0.21.1",
"bulma": "^0.9.4",
"core-js": "^3.6.5",
"core-js": "^3.47.0",
Copy link

@gemini-code-assist gemini-code-assist bot Dec 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This is a very large version jump for core-js (from 3.14.0 to 3.47.0), spanning 88 releases. While this is not a major version bump according to semver, such a large jump can introduce subtle breaking changes or regressions.

For example, I've noticed a few potentially breaking changes in the release notes that might affect your project:

  • Iterator.prototype.sliding removed (in v3.46.0): This was part of a TC39 proposal and has been replaced by an extra parameter on Iterator.prototype.windows. If you were using the sliding polyfill, your code will break.
  • Math.clamp replaced (in v3.43.0): The polyfill for Math.clamp has been replaced with Number.prototype.clamp to follow the TC39 proposal. If your code uses Math.clamp, it will need to be updated.
  • @@species pattern removed (in v3.39.0): The @@species pattern was removed from several %TypedArray% and ArrayBuffer methods. If you have custom subclasses of these built-ins and rely on @@species for constructor selection, this could break your code.

Given the number of changes, thorough regression testing is crucial to mitigate the risk of introducing regressions, especially on all supported target browsers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@nejidevelops @snyk-bot