@sveltejs/vite-plugin-svelte@1.0.0-next.24

Patch Changes

• Only add all Svelte dependencies to ssr.noExternal in SSR build (#169)

@sveltejs/vite-plugin-svelte@1.0.0-next.23

Patch Changes

• Svelte libraries without any Svelte components are also added to ssr.noExternal (#166)

@sveltejs/vite-plugin-svelte@1.0.0-next.22

Patch Changes

• Only optimize nested cjs dependencies (#163)

@sveltejs/vite-plugin-svelte@1.0.0-next.21

Minor Changes

• Add option disableDependencyReinclusion to offer users a way out of automatic optimization for hybrid packages (#161)

Patch Changes

• Improve automatic dependency pre-bundling by not reincluding dependencies that are already present in optimizeDeps.exclude (#159)

@sveltejs/vite-plugin-svelte@1.0.0-next.20

Major Changes

• Enable optimization for nested dependencies of excluded svelte dependencies (#157)

  Vite 2.5.3 and above is needed to support this feature.

Minor Changes

• Improve dev warning message for components including only unscoped styles (fixes #153) (#154)

@sveltejs/vite-plugin-svelte@1.0.0-next.19

Patch Changes

• add automatically excluded svelte dependencies to ssr.noExternal (#147)

@sveltejs/vite-plugin-svelte@1.0.0-next.18

Minor Changes

• automatically exclude svelte dependencies in vite.optimizeDeps (#145)

Patch Changes

• use createRequire to load svelte.config.cjs in esm projects (fixes #141) (#142)

@sveltejs/vite-plugin-svelte@1.0.0-next.17

Patch Changes

• don't add svelte/ssr to vite.optimizeDeps.include (fixes #138) (#139)

@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

• prepare for a change in vite 2.5.0 that would lead to errors in preprocessor dependency handling (fixes #130) (#131)

@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

• resolve vite.root option correctly (fixes #113) (#115)