Tests / @ogygia/jumpstart

@ogygia/jumpstart

Version 0.14.0 latest
commit 620ddcca
34 test runs (34 tests, each run in Node, the browsers or both)
1.98× lines of test for each line of source (1,014 to 512) Only real test code counts: test files and their helpers, not fixtures, sample apps or benches. Blank lines are left out on both sides.
Exactly what is counted non-blank lines of test code across the repo (*.test.ts, *.test-d.ts, *.spec.ts, and the .ts helpers in test/ and e2e/ folders; no fixtures, fixture apps, stubs or benches), over non-blank lines of packages/*/src (no .d.ts or generated files)
89.9% of source lines run by the tests
  • 25Unit
  • 0Browser
  • 9End to end
  • 0Type tests
  • 0Lint rules
  • 0Failing

Coverage

  • 89.9%Lines
  • 88.9%Branches
  • 71.8%Functions
  • 89.8%Statements

Every test

34 tests

TestKindNodeChromiumFirefoxWebKit
packages/jumpstart/e2e/canary.spec.ts
strictExecutionOrder still deadlocks the SvelteKit 2 server build (rolldown#11702)End to endnot runpassskipskip
packages/jumpstart/e2e/jumpstart.spec.ts
a dependency that reads a file beside itself breaks bundled, and works listed in externalEnd to endnot runpassskipskip
a light page never loads the registry chunk; the CMS page loads it and a handful of filesEnd to endnot runpassskipskip
an app with no regions builds with no registry chunk, its pages the sameEnd to endnot runpassskipskip
dev is untouched: the dev server serves every page as without jumpstartEnd to endnot runpassskipskip
every page, and the hole it asks for, is served byte for byte as without jumpstartEnd to endnot runpassskipskip
the build says, in one coded line, what stayed outside the bundle and whyEnd to endnot runpassskipskip
the registry's chunk holds every block, and nothing a Svelte module marks or the frameworkEnd to endnot runpassskipskip
the server build is a few files: the framework and dependencies in one, the registry in anotherEnd to endnot runpassskipskip
packages/jumpstart/test/dependencies.test.ts
dependencies > a directory with no package.json lists no dependencyUnitpassnot runnot runnot run
dependencies > a linked package and the packages it links are dependencies, followed through each one's ownUnitpassnot runnot runnot run
dependencies > an app inside the package it links is the app's code, the rest of that package a dependencyUnitpassnot runnot runnot run
packages/jumpstart/test/externals.test.ts
the external report > counts packages only: relative paths, absolute paths and Node's own modules are notUnitpassnot runnot runnot run
the external report > names the package of a bare specifierUnitpassnot runnot runnot run
the external report > prints one coded line with every package and its reason, sortedUnitpassnot runnot runnot run
the external report > says so when every dependency is inside the bundle (never silent)Unitpassnot runnot runnot run
the external report > says why each package stayed out: the option first, then the Vite config, else ViteUnitpassnot runnot runnot run
packages/jumpstart/test/options.test.ts
options > a misspelled option fails the build instead of being ignoredUnitpassnot runnot runnot run
options > external defaults to none, and a name listed twice is kept onceUnitpassnot runnot runnot run
options > external that is not a list of names fails the buildUnitpassnot runnot runnot run
options > jumpstart() is an ogygia plugin and a Vite plugin that applies to builds onlyUnitpassnot runnot runnot run
packages/jumpstart/test/regions.test.ts
region groups > a registry named like a reserved chunk (shared.ts, server.ts) never shares its name, so light pages never load itUnitpassnot runnot runnot run
region groups > a script registry gets one group: itself, its components and the modules minted for themUnitpassnot runnot runnot run
region groups > a Svelte module that marks regions gets no group, and a component it marks stays out of every groupUnitpassnot runnot runnot run
region groups > cleans a module id: no NUL prefix, no query, forward slashesUnitpassnot runnot runnot run
region groups > no registry file name can produce a reserved chunk nameUnitpassnot runnot runnot run
region groups > reads the live table again after reset (a second build sees regions found later)Unitpassnot runnot runnot run
region groups > two registries get a group each, a shared component goes with the first by path, and names never collideUnitpassnot runnot runnot run
the shared chunk > an entry that imports a block only through the registry shares nothing with itUnitpassnot runnot runnot run
the shared chunk > app code a registry and a page outside it both import is shared; what only the registry reaches is notUnitpassnot runnot runnot run
packages/jumpstart/test/server-chunks.test.ts
the server chunks > a dependency goes in the framework chunk, unless a region is built from itUnitpassnot runnot runnot run
the server chunks > only the server environment of a build is shaped: the client build and dev get nothingUnitpassnot runnot runnot run
the server chunks > the built graph is read into the shared chunkUnitpassnot runnot runnot run
the server chunks > the external report skips the build’s own chunks and Node’s modulesUnitpassnot runnot runnot run