Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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@7.0.0
Major Changes
#1309
fdafb6d
Thanks @mrm007! - Use absolute paths internally to make sure Vite resolves modules correctlyThis change only affects integrations that use the vite-node compiler, which is currently the esbuild (next) and Vite plugins
@vanilla-extract/esbuild-plugin@2.3.5
Patch Changes
fdafb6d
]:@vanilla-extract/jest-transform@1.1.4
Patch Changes
fdafb6d
]:@vanilla-extract/parcel-transformer@1.0.4
Patch Changes
fdafb6d
]:@vanilla-extract/rollup-plugin@1.3.4
Patch Changes
fdafb6d
]:@vanilla-extract/vite-plugin@4.0.3
Patch Changes
#1309
fdafb6d
Thanks @mrm007! - Correctly resolve module paths when using Vite plugins that affect module resolution, such asvite-tsconfig-paths
#1308
20e33a5
Thanks @mrm007! - Don't pass Remix Vite plugin to the vite-node compilerRemix throws an error if it's loaded without a config file, which is what we do when we initialise the vite-node compiler.
Updated dependencies [
fdafb6d
]:@vanilla-extract/webpack-plugin@2.3.6
Patch Changes
fdafb6d
]:@vanilla-extract/esbuild-plugin-next@0.0.5
Patch Changes
#1309
fdafb6d
Thanks @mrm007! - Correctly resolve module paths when using Vite plugins that affect module resolution, such asvite-tsconfig-paths
Updated dependencies [
fdafb6d
]: