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.

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

[Snyk] Upgrade: , core-js, esbuild, vite, vite-plugin-vuetify #10

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

[Snyk] Upgrade: , core-js, esbuild, vite, vite-plugin-vuetify #10

wants to merge 1 commit into from

Conversation

ispyhumanfly
Copy link

snyk-top-banner

Snyk has created this PR to upgrade multiple dependencies.

👯 The following dependencies are linked and will therefore be updated together.

ℹ️ 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.

Name Versions Released on

@vitejs/plugin-vue
from 5.1.0 to 5.1.2 | 2 versions ahead of your current version | a month ago
on 2024-08-01
core-js
from 3.37.1 to 3.38.1 | 2 versions ahead of your current version | a month ago
on 2024-08-20
esbuild
from 0.23.0 to 0.23.1 | 1 version ahead of your current version | a month ago
on 2024-08-16
vite
from 5.3.4 to 5.4.2 | 6 versions ahead of your current version | a month ago
on 2024-08-20
vite-plugin-vuetify
from 2.0.3 to 2.0.4 | 1 version ahead of your current version | a month ago
on 2024-08-04

Release notes
Package name: @vitejs/plugin-vue from @vitejs/plugin-vue GitHub release notes
Package name: core-js from core-js GitHub release notes
Package name: esbuild
  • 0.23.1 - 2024-08-16

    • Allow using the node: import prefix with es* targets (#3821)

      The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

      // Original code
      import fs from 'node:fs'
      fs.open

      // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
      import fs from "fs";
      fs.open;

      // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
      import fs from "node:fs";
      fs.open;

    • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

      Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

    • Fix incorrect location of certain error messages (#3845)

      This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

    • Print comments before case clauses in switch statements (#3838)

      With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

    • Fix a memory leak with pluginData (#3825)

      With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

  • 0.23.0 - 2024-07-02

    This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

    • Revert the recent change to avoid bundling dependencies for node (#3819)

      This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

      I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

      In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

    • Fix preserving collapsed JSX whitespace (#3818)

      When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

      // Original code
      <Foo>
      <Bar />
      </Foo>

      // Old output (with --jsx=preserve)
      <Foo><Bar /></Foo>;

      // New output (with --jsx=preserve)
      <Foo>
      <Bar />
      </Foo>;

from esbuild GitHub release notes
Package name: vite from vite GitHub release notes
Package name: vite-plugin-vuetify from vite-plugin-vuetify 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 multiple dependencies with Snyk
0bcf3d9 
Snyk has created this PR to upgrade:
  - @vitejs/plugin-vue from 5.1.0 to 5.1.2.
    See this package in npm: https://www.npmjs.com/package/@vitejs/plugin-vue
  - core-js from 3.37.1 to 3.38.1.
    See this package in npm: https://www.npmjs.com/package/core-js
  - esbuild from 0.23.0 to 0.23.1.
    See this package in npm: https://www.npmjs.com/package/esbuild
  - vite from 5.3.4 to 5.4.2.
    See this package in npm: https://www.npmjs.com/package/vite
  - vite-plugin-vuetify from 2.0.3 to 2.0.4.
    See this package in npm: https://www.npmjs.com/package/vite-plugin-vuetify

See this project in Snyk:
https://app.snyk.io/org/barton-malow-data-and-automation/project/8bf6e0db-f77c-46f4-85c7-7555992b9d44?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ispyhumanfly @snyk-bot