8000 Tags · colinhacks/motherload · GitHub
[go: up one dir, main page]

Skip to content

Tags

Tags

v0.4.1

Toggle v0.4.1's commit message

Verified

This commit was signed with the committer’s verified signature.
colinhacks Colin McDonnell
Every package is at 0.4.1, for the release of the Vite dev-server gua…

…rd that sends no .env file, whatever its name (44c85d1), and the README's "Best for scripts" note on .env, at the maintainer's word of 2026-11-04 ("Release 0.4.1 now") (nub run bump 0.4.1). Verified: nub run typecheck; nub run test, 96 passed, none skipped.

v0.4.0

Toggle v0.4.0's commit message

Verified

This commit was signed with the committer’s verified signature.
colinhacks Colin McDonnell
A missing .env file always fails the type check and the build: the st…

…rict option of 0ee1494 is gone, at the maintainer's word of 2026-11-03, "drop this option entirely and always operate in strict mode, which I think is clearly the best idea". No release carried it (v0.3.0 came before it, and the 0.4.0 release run 41689976109 at 4293b21 was cancelled for this change). packages/core/src/tsconfig.ts, which each host used to read the option from tsconfig after an import of a missing .env file failed, is deleted, with the Node resolve hook, the Bun and esbuild onResolve and the Vite plugin's resolveId that let such a file through, the loader contract's opti
8000
onal and combine's passing of it, and the .env loader's; the mapper reports any key in a tsconfig entry's options as before ("Motherload takes no options"). The host argument of 468e674 ({ bundle }), RUNTIME and BUNDLE, and the .env module's bundle branch stay as they are. The docs page and the README lose the strict example and the line on webpack, Rspack and Jest under it; the local.env and .env.local examples stay. DESIGN.md's ".env module" records the decision with the maintainer's answer of the same day on the docs' local.env, which a fresh clone lacks ("I think it's kind of inevitable. I think we should keep things strict. This is honestly kind of just intended for development scripts, I feel like"), and the rejected option with its measurements; "The mapper process" is "No options" again; PLAN.md marks the 2026-10-28 decision replaced and adds the 2026-11-03 one, folding in bd48b68's bullet; AGENTS.md's layout drops tsconfig.ts. tests/strict.test.ts, the mapper's strict test, the data test's line on a let-through file and the onResolve stubs in the adapter and package tests are removed. Verified: nub run typecheck; nub run test, 95 passed, none skipped; nub run build in site/. A first full run was stopped after an hour with tests/lab.test.ts still running; run alone with a five-minute per-test timeout it passed all 22 tests, and the full run that followed passed.

v0.3.0

Toggle v0.3.0's commit message

Verified

This commit was signed with the committer’s verified signature.
colinhacks Colin McDonnell
Every package is at 0.3.0, for the release of motherload/next (withMo…

…therload, 429a8f7), the end-of-file diagnostic fix (5e3af83) and the Vitest cache fix (9ee97e4), at the maintainer's word of 2026-10-26 ("cut a releease if needed") (nub run bump 0.3.0). Verified: nub run typecheck; nub run test, 95 passed, none skipped.

v0.2.0

Toggle v0.2.0's commit message

Verified

This commit was signed with the committer’s verified signature.
colinhacks Colin McDonnell
Every package is at 0.2.0, for the release of motherload/webpack, mot…

…herload/turbopack, motherload/vite and motherload/jest and each format package's own (nub run bump 0.2.0). Verified: CI run 39669622440 green at 1dadaab, the commit before this one.

v0.1.0

Toggle v0.1.0's commit message

Verified

This commit was signed with the committer’s verified signature.
colinhacks Colin McDonnell
Every package is at 0.1.0, the maintainer's instruction of 2026-10-21…

…: "lets cut 0.1" (nub run bump 0.1.0). Ten packages now that JSON Schema left for dotschema: motherload, @motherload/core and the eight format packages. Verified at 0.1.0: nub run typecheck; nub run test, 53 of 53; nub run build and nub run check-dist.

v0.0.1

Toggle v0.0.1's commit message

Verified

This commit was signed with the committer’s verified signature.
colinhacks Colin McDonnell
Schemas stay in `motherload`, the maintainer's answer of 2026-10-21 (…

…"Keep it in `motherload`") to whether to take JSON Schema support out of the `motherload` package before 0.0.1 is published. The alternatives were `motherload` as the eight data formats with `@motherload/schema` installed beside it (its own tsconfig entry, preload, esbuild plugin and mapper process, a combination lab/packages already runs), and a product of its own, as Reylo is for SQL. DESIGN.md's Packaging section records the answer with what was measured that day: the schema package was 1,828 of the 2,708 lines of package source and its four test files 1,626 of the 2,306 lines of tests; ajv and ajv-formats were about 1.09 MB of `motherload`'s install; a bundled schema module imports nothing, while under the preload ajv compiles the schema in the project's process (87 files, about 46 ms for one schema, refused under --disallow-code-generation-from-strings); and npm held only the 0.0.0 placeholders. PLAN.md's package-family decision notes it. Docs only; verified: nub run typecheck; nub run test.
0