@foldkit/vite-plugin 0.26.0-canary.26e27fd937f9 → 0.26.0-canary.482593707a08

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/index.js +11 -11
  2. package/package.json +3 -3
package/dist/index.js CHANGED
@@ -18,16 +18,15 @@ export { brandDistDirectory } from './brandDist.js';
18
18
  export { FOLDKIT_FETCH_MODULE_ID, FoldkitBuildManifest, FoldkitBuildMetadata, foldkitBuild, } from './build.js';
19
19
  export { foldkitSsr } from './ssr.js';
20
20
  export { foldkitViewIdentity, transformViewIdentity, } from './viewIdentity.js';
21
- // NOTE: Vite's dep optimizer scans the consumer's source for `effect`
22
- // imports and pre-bundles only those exports into a single `effect.js`
23
- // blob. It does not follow imports through workspace/node_modules
24
- // packages, so any `effect` namespace foldkit's compiled dist references
25
- // that the consumer does not mention by name is missing from the blob
26
- // and crashes at runtime in dev. The list below covers every top-level
27
- // namespace foldkit imports from bare `'effect'`. Over-inclusion is
28
- // harmless; under-inclusion is the bug. Kept in sync with foldkit's
29
- // source by `scripts/check-effect-prebundle.ts` (runs in `pnpm check`).
30
- const FORCE_INCLUDED_EFFECT_NAMESPACES = [
21
+ // NOTE: Vite does not scan imports through `foldkit` because the plugin
22
+ // excludes the package from optimization. A consumer can import only Effect
23
+ // subpaths while Foldkit's compiled distribution imports the bare barrel, so
24
+ // include both the barrel and every top-level namespace Foldkit imports. This
25
+ // keeps them in one optimized dependency graph. Over-inclusion is harmless;
26
+ // under-inclusion is the bug. `scripts/check-effect-prebundle.ts` keeps the
27
+ // entries in sync with Foldkit's source and runs in `pnpm check`.
28
+ const FORCE_INCLUDED_EFFECT_ENTRIES = [
29
+ 'effect',
31
30
  'effect/Array',
32
31
  'effect/Boolean',
33
32
  'effect/Cause',
@@ -55,6 +54,7 @@ const FORCE_INCLUDED_EFFECT_NAMESPACES = [
55
54
  'effect/PubSub',
56
55
  'effect/Queue',
57
56
  'effect/Record',
57
+ 'effect/Redacted',
58
58
  'effect/Ref',
59
59
  'effect/Result',
60
60
  'effect/Runtime',
@@ -515,7 +515,7 @@ export const foldkit = (options = {}) => {
515
515
  apply: 'serve',
516
516
  config: () => ({
517
517
  optimizeDeps: {
518
- include: [...FORCE_INCLUDED_EFFECT_NAMESPACES],
518
+ include: [...FORCE_INCLUDED_EFFECT_ENTRIES],
519
519
  },
520
520
  }),
521
521
  configureServer: server => {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@foldkit/vite-plugin",
3
- "version": "0.26.0-canary.26e27fd937f9",
3
+ "version": "0.26.0-canary.482593707a08",
4
4
  "description": "Vite plugin for Foldkit with state-preserving live reload",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -17,7 +17,7 @@
17
17
  ],
18
18
  "peerDependencies": {
19
19
  "effect": "4.0.0",
20
- "foldkit": "0.165.0-canary.26e27fd937f9",
20
+ "foldkit": "0.165.0-canary.482593707a08",
21
21
  "vite": "^8.0.0"
22
22
  },
23
23
  "dependencies": {
@@ -37,7 +37,7 @@
37
37
  "vite": "^8.3.1",
38
38
  "vite-host": "npm:vite@8.2.1",
39
39
  "vitest": "^4.1.11",
40
- "foldkit": "0.165.0-canary.26e27fd937f9"
40
+ "foldkit": "0.165.0-canary.482593707a08"
41
41
  },
42
42
  "keywords": [
43
43
  "vite",