Releases: sveltejs/vite-plugin-svelte
@sveltejs/vite-plugin-svelte@1.0.0-next.17
@sveltejs/vite-plugin-svelte@1.0.0-next.16
Major Changes
-
automatically include svelte in vite config optimizeDeps.include (#137)
Previously, svelte was automatically excluded. We include it now by default to improve deduplication.
As a result, svelte is pre-bundled by vite during dev, which it logs when starting the devserver
Pre-bundling dependencies: svelte/animate svelte/easing svelte/internal svelte/motion svelte/store (...and 2 more) (this will be run only when your dependencies or config have changed)
And it's also visible in the browsers network tab, where requests for svelte imports now start with
node_modules/.vite/
during dev.Check out the vite pre-bundling documentation for more information.
To get the old behavior back, add the following to your vite config
{ ['svelte']; }
Patch Changes
@sveltejs/vite-plugin-svelte@1.0.0-next.15
Major Changes
-
change default value of compilerOptions.hydratable to false (#122)
This is done to align with svelte compiler defaults and improve output in non-ssr scenarios.
Add
{compilerOptions: {hydratable: true}}
to vite-plugin-svelte config if you need hydration (eg. for ssr)
Minor Changes
- add config option
experimental.dynamicCompileOptions
for finegrained control over compileOptions (#122)
Patch Changes
@sveltejs/vite-plugin-svelte@1.0.0-next.14
@sveltejs/vite-plugin-svelte@1.0.0-next.13
Minor Changes
-
Add
experimental
section to options and moveuseVitePreprocess
there (#99)Experimental options are not ready for production use and breaking changes to them can occur in any release
If you already had
useVitePreprocess
enabled, update you config:- svelte({useVitePreprocess: true}) + svelte({experimental: {useVitePreprocess: true}})
-
Add option to ignore svelte preprocessors of other vite plugins (#98)
- ignore them all:
ignorePluginPreprocessors: true
- ignore by name:
ignorePluginPreprocessors: ['<name of plugin>',...]
- ignore them all:
-
Move plugin preprocessor definition to api namespace (#98)
Plugins that provide
myplugin.sveltePreprocess
, should move it tomyplugin.api.sveltePreprocess
, as suggested by rollup -
Experimental: Generate sourcemaps for preprocessors that lack them (#101)
enable option
experimental.generateMissingPreprocessorSourcemaps
to use it
Patch Changes
@sveltejs/vite-plugin-svelte@1.0.0-next.12
Minor Changes
-
Resolve svelte to svelte/ssr when building for ssr (fixes #74) (#75) (
f6f56fe
) -
Restart dev server when svelte config file changes (#72) (
5100376
) -
Allow svelte imports to be added to optimizeDeps.include and don't exclude svelte from optimizeDeps then (#68) (
9583900
) -
Vite config can be updated based on values in svelte config (see #60) (#64) (
c3f65fd
)
Patch Changes
@sveltejs/vite-plugin-svelte@1.0.0-next.11
Major Changes
-
#54
0f7e256
feat: convert to es module with cjs fallback, use named export instead of defaultIf you are using vite-plugin-svelte with require, you should switch to esm and import the named export "svelte".
An example can be found in the usage section of the readmeFor existing esm configs update your import to use the new named export.
- import svelte from '@sveltejs/vite-plugin-svelte'; + import { svelte } from '@sveltejs/vite-plugin-svelte';
continuing with cjs/require is discouraged but if you must use it, update your require statement to use the named export
- const svelte = require('@sveltejs/vite-plugin-svelte'); + const { svelte } = require('@sveltejs/vite-plugin-svelte');
Minor Changes
- #45
673cf61
Feature: log svelte compiler warnings to console. use options.onwarn to customize logging