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

chore(deps): update dependency @vanilla-extract/vite-plugin to v4 #51

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

chore(deps): update dependency @vanilla-extract/vite-plugin to v4 #51

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 2, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vanilla-extract/vite-plugin (source) ^3.8.0 -> ^4.0.0 age adoption passing confidence

Release Notes

vanilla-extract-css/vanilla-extract (@​vanilla-extract/vite-plugin)

v4.0.17

Compare Source

Patch Changes

v4.0.16

Compare Source

Patch Changes

v4.0.15

Compare Source

Patch Changes

v4.0.14

Compare Source

Patch Changes

v4.0.13

Compare Source

Patch Changes

v4.0.12

Compare Source

Patch Changes

v4.0.11

Compare Source

Patch Changes

v4.0.10

Compare Source

Patch Changes

v4.0.9

Compare Source

Patch Changes

v4.0.8

Compare Source

Patch Changes

v4.0.7

Compare Source

Patch Changes

v4.0.6

Compare Source

Patch Changes

v4.0.5

Compare Source

Patch Changes
  • #​1353 94d5f06 Thanks @​himself65! - Move vite-node compiler creation to a more appropriate plugin hook to ensure correct cleanup of resources

v4.0.4

Compare Source

Patch Changes

  • #​1314 e8a6850 Thanks @​mrm007! - Resolve and pass a new copy of the Vite config to the vite-node compiler

    Previously, we were passing the same Vite config object to the vite-node compiler. This was causing compatibility issues with other plugins, such as Vitest and Remix.

  • Updated dependencies [e8a6850]:

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes

  • #​1304 545bf82 Thanks @​fukumasuya! - Pass Vite resolve config to vite-node compiler

    The plugin passes through the project's Vite resolve config to the vite-node compiler, which will be used for resolving imports. These options include [resolve.alias][resolve.alias], [resolve.dedupe][resolve.dedupe], [resolve.conditions][resolve.conditions], [resolve.mainFields][resolve.mainFields], [resolve.extensions][resolve.extensions], and others.

  • Updated dependencies [545bf82]:

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes

  • #​1264 e531c41 Thanks @​mrm007! - The Vite plugin now uses a newer, faster, Vite-based compiler by default.

    The new compiler uses vite-node to parse and extract CSS from .css.ts files. This comes with all the benefits of using Vite, faster builds and the ability to use Vite plugins.

    The new compiler has been used in Remix ever since support for Vanilla Extract was introduced.

  • #​1264 e531c41 Thanks @​mrm007! - The behaviour previously known as emitCssInSsr has been turned on by default. The emitCssInSsr option has been removed.

    This means that the CSS emitted by the plugin is now processed by Vite, so the plugin no longer needs to resolve PostCSS plugins and process the CSS output itself.

  • #​1264 e531c41 Thanks @​mrm007! - The esbuildOptions option has been removed as we are no longer using esbuild internally

  • #​1264 e531c41 Thanks @​mrm007! - Drop support for Vite < 4

Patch Changes

v3.9.5

Compare Source

Patch Changes

v3.9.4

Compare Source

Patch Changes

v3.9.3

Compare Source

Patch Changes

v3.9.2

Compare Source

Patch Changes

v3.9.1

Compare Source

Patch Changes

v3.9.0

Compare Source

Minor Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Feb 2, 2024

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN cli npm v10.4.0 does not support Node.js v16.20.1. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @vitejs/plugin-react@3.1.0
npm WARN Found: vite@5.0.12
npm WARN node_modules/vite
npm WARN   dev vite@"^5.0.12" from the root project
npm WARN   9 more (@joshwooding/vite-plugin-react-docgen-typescript, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer vite@"^4.1.0-beta.0" from @vitejs/plugin-react@3.1.0
npm WARN node_modules/@storybook/react-vite/node_modules/@vitejs/plugin-react
npm WARN   @vitejs/plugin-react@"^3.0.1" from @storybook/react-vite@7.6.12
npm WARN   node_modules/@storybook/react-vite
npm WARN 
npm WARN Conflicting peer dependency: vite@4.5.2
npm WARN node_modules/vite
npm WARN   peer vite@"^4.1.0-beta.0" from @vitejs/plugin-react@3.1.0
npm WARN   node_modules/@storybook/react-vite/node_modules/@vitejs/plugin-react
npm WARN     @vitejs/plugin-react@"^3.0.1" from @storybook/react-vite@7.6.12
npm WARN     node_modules/@storybook/react-vite
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: vite@5.0.12
npm ERR! notsup Not compatible with your version of node/npm: vite@5.0.12
npm ERR! notsup Required: {"node":"^18.0.0 || >=20.0.0"}
npm ERR! notsup Actual:   {"npm":"10.4.0","node":"v16.20.1"}

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-02T23_13_29_060Z-debug-0.log
File name: pnpm-lock.yaml
Progress: resolved 0, reused 0, downloaded 1, added 0
Progress: resolved 55, reused 0, downloaded 55, added 0
Progress: resolved 183, reused 0, downloaded 167, added 0
Progress: resolved 411, reused 0, downloaded 396, added 0
undefined
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing the dependencies of @vanilla-extract/vite-plugin@4.0.2
 at @vanilla-extract/integration@6.5.0

Your Node version is incompatible with "registry.npmjs.org/vite-node/1.2.2".

Expected version: ^18.0.0 || >=20.0.0
Got: v16.20.1

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Feb 2, 2024

⚠️ No Changeset found

Latest commit: 241a53a

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

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.
0 participants