Skip to content

[Snyk] Upgrade terser from 5.19.0 to 5.19.4 #47

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

Merged
merged 1 commit into from
Oct 9, 2023

Conversation

Woodpile37
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade terser from 5.19.0 to 5.19.4.

ℹ️ 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 4 versions ahead of your current version.
  • The recommended version was released a month ago, on 2023-09-04.
Release notes
Package name: terser from terser GitHub release notes
Commit messages
Package name: terser

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@changeset-bot
Copy link

changeset-bot bot commented Oct 9, 2023

⚠️ No Changeset found

Latest commit: 35af48b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codeautopilot
Copy link

codeautopilot bot commented Oct 9, 2023

Pull Request Summary

This Pull Request is an automated upgrade request created by Snyk to upgrade the terser package from version 5.19.0 to version 5.19.4. The recommended version is 4 versions ahead of the current version and was released a month ago on September 4, 2023.

The changes in this Pull Request include modifications to the package-lock.json and package.json files. In the package-lock.json file, the resolved URLs and integrity hashes for the @jridgewell/gen-mapping, @jridgewell/resolve-uri, @jridgewell/set-array, @jridgewell/source-map, @jridgewell/trace-mapping, acorn, acorn-jsx, buffer-from, builtin-modules, commander, concat-map, esutils, fast-deep-equal, fast-json-stable-stringify, find-up, fs.realpath, glob, graceful-fs, has-flag, inflight, inherits, is-binary-path, is-plain-object, is-stream, isexe, json-parse-better-errors, json-schema-traverse, json-stable-stringify-without-jsonify, json5, kind-of, lodash, lodash.debounce, lodash.memoize, lodash.uniq, minimatch, minimist, mkdirp, ms, node-fetch, normalize-package-data, npm-run-path, object-assign, once, os-tmpdir, p-limit, p-locate, p-try, path-exists, path-is-absolute, path-key, path-parse, path-type, picomatch, process-nextick-args, promise-inflight, pseudomap, readable-stream, readdirp, resolve, resolve-from, rimraf, safe-buffer, semver, source-map, source-map-support, terser, terser-webpack-plugin, through2, to-absolute-glob, to-fast-properties, trim-newlines, tslib, typescript, uglify-js, util-deprecate, v8-compile-cache, which, which-module, worker-farm, wrappy, write-file-atomic, yargs, and yargs-parser packages have been updated. In the package.json file, the terser package version has been updated to 5.19.4.

The purpose of this Pull Request is to keep the dependencies up-to-date, making it easier to fix existing vulnerabilities and quickly identify and fix newly disclosed vulnerabilities that may affect the project.

The impact of this Pull Request is that the terser package will be upgraded to the latest version, which may include bug fixes, performance improvements, and new features. It is important to review the release notes of the terser package to understand the specific changes and improvements introduced in version 5.19.4.


Current plan usage: 51.21%


Have feedback or need help?

Discord
Documentation
[email protected]

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