Releases: vanilla-extract-css/vanilla-extract
@vanilla-extract/[email protected]
Patch Changes
- #428
e915f7fThanks @mattcompiles! - Ensure whitespace is stripped from debug Ids
@vanilla-extract/[email protected]
Major Changes
- #422
4e5ba05Thanks @mattcompiles! - Remove thedevStyleRuntimeoption
Patch Changes
-
#422
4e5ba05Thanks @mattcompiles! - Fix HMR for pre-existing CSSPreviously, styles would not hot reload correctly when returning to a previously cached version
@vanilla-extract/[email protected]
Patch Changes
- #335
2e86d9aThanks @jonathantneal! - Fix CSS not outputting on SSR builds
@vanilla-extract/[email protected]
Patch Changes
-
#416
65d0840Thanks @benjervis! - Allow explicit false variants.Boolean variants in recipes can now also have a
falsecase, which is handled properly by the type system and the build system.
@vanilla-extract/[email protected]
Patch Changes
-
#409
a9c5cb7Thanks @benjervis! - Fix plugin for watch mode.The vite plugin previously relied on a one to one matching of resolve to load calls, and would clean up the CSS stored in memory after it was loaded.
This isn't true in
--watchmode, as the same file can be loaded on the rebuild without having to be resolved, which the plugin now handles. -
#409
a9c5cb7Thanks @benjervis! - Update the "vanilla-extract" devStyleRuntime option.When using the vanilla browser runtime in vite, it now operates on a new model where a .css.js file is generated, that uses @vanilla-extract/css/injectStyles to add the css to the browser.
This allows for hot reloading of styles, and makes styles a bit easier to debug at dev time (because they're actually visible).
-
#409
a9c5cb7Thanks @benjervis! - Handle vite 2.6.As of vite 2.6 and greater,
?usedgets appended to css imports, which causes the file imports to be not what we expected.This caused mismatching classnames in the vite plugin, and it caused the babel plugin to not add filescopes when it should have.
-
#409
a9c5cb7Thanks @benjervis! - Automatically optimize deps.When using the new vanilla browser runtime, the new
injectStylesdependency gets injected at runtime, so vite can't discover it ahead of time and pre-bundle it.The plugin will now add the dependency to optimizeDeps if the vanilla runtime is being used so that it's optimized up front.
It also ensures that some relevant vanilla packages are externalised in SSR mode. -
Updated dependencies [
a9c5cb7]:- @vanilla-extract/[email protected]
@vanilla-extract/[email protected]
Patch Changes
-
#409
a9c5cb7Thanks @benjervis! - Export the fileScope functions.stringifyFileScopeandparseFileScopeare now exported to be used in other packages. -
Updated dependencies [
a9c5cb7]:- @vanilla-extract/[email protected]
@vanilla-extract/[email protected]
Patch Changes
-
#409
a9c5cb7Thanks @benjervis! - Improve the browser runtime dev experience.The vanilla browser runtime now creates style tags containing the CSS itself, rather than injecting it directly into the CSSOM.
This helps with debugability, as the generated CSS can actually be seen in the devtools.
There are also some new attributes set on the style tags, making it easier to identify the source of each style.
@vanilla-extract/[email protected]
Patch Changes
-
#409
a9c5cb7Thanks @benjervis! - Handle vite 2.6.As of vite 2.6 and greater,
?usedgets appended to css imports, which causes the file imports to be not what we expected.This caused mismatching classnames in the vite plugin, and it caused the babel plugin to not add filescopes when it should have.
-
Updated dependencies [
a9c5cb7]:- @vanilla-extract/[email protected]
@vanilla-extract/[email protected]
Patch Changes
-
#398
63f4ed0Thanks @benjervis! - Fixes a bug with vite where "?used" is appended to the file path of css files.This could cause different class name hashes to be generated between SSR and client builds.
This was introduced in vite 2.6.0.
@vanilla-extract/[email protected]
Patch Changes
-
#393
2f379f1Thanks @mattcompiles! - Fix compilation errors in Vite 2.6 -
Updated dependencies [
2f379f1]:- @vanilla-extract/[email protected]