Version Packages

[vanilla-extract-ci]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@vanilla-extract/integration@6.5.0

Minor Changes

• #1304 545bf82 Thanks @fukumasuya! - Add a viteResolve option to the vite-node compiler

  This allows integrations to provide a Vite resolve config to the vite-node compiler, which will be used for resolving imports. These options include resolve.alias, resolve.dedupe, resolve.conditions, resolve.mainFields, resolve.extensions, and others.

@vanilla-extract/next-plugin@2.3.6

Patch Changes

• #1247 f0c3be9 Thanks @askoufis! - Fixes a bug that was causing style compilation to fail on paths containing webpack template strings such as [id] or Next.js dynamic routes such as [slug].

• Updated dependencies [f0c3be9]:

  • @vanilla-extract/webpack-plugin@2.3.5

@vanilla-extract/vite-plugin@4.0.2

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.dedupe, resolve.conditions, resolve.mainFields, resolve.extensions, and others.

• Updated dependencies [545bf82]:

  • @vanilla-extract/integration@6.5.0

@vanilla-extract/webpack-plugin@2.3.5

Patch Changes

• #1247 f0c3be9 Thanks @askoufis! - Fixes a bug that was causing style compilation to fail on paths containing webpack template strings such as [id] or Next.js dynamic routes such as [slug].

• Updated dependencies [545bf82]:

  • @vanilla-extract/integration@6.5.0

[askoufis]

No next plugin release??? 🤔

[mrm007]

No next plugin release??? 🤔

I think you need to manually declare it in a changeset 🤷‍♂️