@vanilla-extract/next-plugin

2.4.0

Minor Changes

#1365 ed67731 Thanks @renrizzolo! - Pages router: use next-style-loader in dev, output css in ssr

2.3.7

Patch Changes

#1333 6ac9f66 Thanks @askoufis! - Use a more accurate regex for detecting webpack template strings in paths

We now use a modified version of the regex from the webpack source code to detect template strings in paths. As long as the path isn't already escaped, we should detect it.
Updated dependencies [6ac9f66]:
- @vanilla-extract/webpack-plugin@2.3.7

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

2.3.5

Patch Changes

#1264 e531c41 Thanks @mrm007! - Update dependencies
Updated dependencies [e531c41]:
- @vanilla-extract/webpack-plugin@2.3.4

2.3.4

Patch Changes

#1291 00af971 Thanks @mrm007! - Update dependency @vanilla-extract/integration
#1254 f373d7f Thanks @EvgenNoskov! - Allow hyphens in class names when using a custom identifier
Updated dependencies [00af971, f373d7f]:
- @vanilla-extract/webpack-plugin@2.3.3

2.3.3

Patch Changes

#1262 610c50b Thanks @mrm007! - Update Babel config to target Node.js 14
Updated dependencies [610c50b]:
- @vanilla-extract/webpack-plugin@2.3.2

2.3.2

Patch Changes

#1193 a22dd4d Thanks @syfxlin! - Fixes Next.js 13.5.x CSS output on Windows when using React Server Components

2.3.1

Patch Changes

#1180 89224fe Thanks @syfxlin! - Fixes Next.js 13 CSS output on Windows when using React Server Components
Updated dependencies [89224fe]:
- @vanilla-extract/webpack-plugin@2.3.1

2.3.0

Minor Changes

#1160 e391bae Thanks @SombreroElGringo! - Users can now provide a custom identifier hashing function

Patch Changes

Updated dependencies [e391bae]:
- @vanilla-extract/webpack-plugin@2.3.0

2.2.2

Patch Changes

#1155 1cb537b Thanks @GeeWizWow! - Fix URL statements not not respecting Next's setup for resolving assets

2.2.1

Patch Changes

#1148 b279bb5 Thanks @mattcompiles! - Fix error when intializing plugin

2.2.0

Minor Changes

#1105 9541d79 Thanks @SukkaW! - Fix #1101. Correctly handle Next.js configuration.

2.1.3

Patch Changes

#1099 0d1c17a Thanks @shuding! - Use the resolved Next.js config in next-plugin

2.1.2

Patch Changes

#1060 71f1dc5 Thanks @SuttonJack! - Prepare next-plugin for Next 13 App Dir support

#912 9cefba8 Thanks @nix6839! - Add types to Nextjs plugin configuration

2.1.1

Patch Changes

#852 dfc6405 Thanks @mattcompiles! - Fix Cannot find module *.css.ts.vanilla.css issue

Previously, CSS was being output on both the client and server builds. This fix ensure CSS is only output on the client build.

2.1.0

Minor Changes

#827 9cfb9a1 Thanks @mattcompiles! - Remove requirement for @vanilla-extract/babel-plugin

Previously, to get automatic debug IDs you needed to use Babel with the @vanilla-extract/babel-plugin in your config. As this is no longer the case, the @vanilla-extract/babel-plugin should be removed completely from your project.

Patch Changes

Updated dependencies [9cfb9a1]:
- @vanilla-extract/webpack-plugin@2.2.0

2.0.2

Patch Changes

#645 5ebca75 Thanks @mattcompiles! - Bump @vanilla-extract/integration dep
Updated dependencies [5ebca75]:
- @vanilla-extract/webpack-plugin@2.1.7

2.0.1

Patch Changes

#543 2c7abb1 Thanks @mattcompiles! - Ensure code is compatible with node 12
Updated dependencies [2c7abb1]:
- @vanilla-extract/webpack-plugin@2.1.5

2.0.0

Major Changes

#537 014f551 Thanks @mattcompiles! - Bump minimum version of Next to 12.0.5.

1.0.1

Patch Changes

#443 18363ee Thanks @swudged! - Support Next.js v12