Version Packages - #47
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
21 times, most recently
from
June 8, 2026 14:34
ddf6c99 to
b03d248
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
9 times, most recently
from
June 11, 2026 19:30
218c1d4 to
e2c5f5d
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
11 times, most recently
from
June 26, 2026 13:33
43c4293 to
0db0358
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
June 26, 2026 15:30
208c76e to
13b7af1
Compare
This was referenced Jul 6, 2026
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 20, 2026 18:34
13b7af1 to
f6b210e
Compare
jodeleeuw
added a commit
that referenced
this pull request
Jul 20, 2026
* docs: add repository review and prioritized improvement plan Full review of all three packages, the open PRs (#132, #133, #47), and repo infrastructure. Documents verified data-loss bugs, performance issues affecting #95, CI gaps, test coverage gaps, and feature opportunities, organized into six phased workstreams. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QMjKvi9vHT3LfikGfW84Kg * docs: note open Dependabot alerts and behind-major dependency stack in plan Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QMjKvi9vHT3LfikGfW84Kg --------- Co-authored-by: Claude <noreply@anthropic.com>
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
July 20, 2026 21:48
2309968 to
8ab1cdc
Compare
jodeleeuw
added a commit
that referenced
this pull request
Jul 20, 2026
…, README (#137) * ci: add typecheck and lint gates, refresh node test matrix CI never ran tsc or eslint, so type errors and lint violations (including an untypechecked packages/cli) could land silently. Add a `typecheck` script to every package (tsc --noEmit, or the frontend's existing `tsc -b` project setup) plus a root script that runs them all, wire both typecheck and `lint --workspaces --if-present` into the Build job, and bump the pinned Node 20.x (EOL) to a 22.x/24.x matrix for the Test job. Fixing packages/cli's typecheck required skipLibCheck (an @types/node version bump introduced generic TypedArrays that conflict with this tsconfig's ES2018 lib under this TypeScript version — the frontend tsconfig already carries the same flag) and a narrow `as any` cast in one test assertion where the library's own return type is untyped `{}`. Making frontend lint pass in CI required replacing a handful of `any`-typed showSaveFilePicker/webkitdirectory workarounds with narrow structural types, and scoping the lint script to src/ (tests aren't typechecked by this project either, so this mirrors existing convention) with a small --max-warnings allowance for the pre-existing react-hooks/ react-refresh warnings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QMjKvi9vHT3LfikGfW84Kg * fix(metadata,cli): correct package metadata packages/metadata's repository/bugs URLs pointed at jspsych/jsPsych (the wrong repo) and would leak that to npm on publish; point them at jspsych/metadata instead. Reorder the exports map so the "types" condition comes first — TS condition matching is order-sensitive, so a trailing "types" entry can be skipped. Drop the dead build:types script (references a nonexistent tsconfig.build.json and isn't part of the build chain) and the vestigial husky devDependency (no .husky/ directory in this repo). packages/cli depended on "@jspsych/metadata": "*", which would happily resolve to an incompatible future major. Pin it to the 0.0.x/0.1.x line (0.1.0 is the pending release in PR #47) rather than a bare "^0.1.0": until that release ships, the local workspace package is still at 0.0.3, and a range that excludes it breaks `npm install` for local dev and CI alike since npm workspaces only symlinks a dependency when the workspace version satisfies the declared range. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QMjKvi9vHT3LfikGfW84Kg * docs: expand root README, drop ignored build flag The root README was two lines; expand it into a proper overview (what the project is, the monorepo layout, a CLI quick-start, links to the docs/ guides, and dev/contributing commands) without turning it into a duplicate of the package-level READMEs. Also drop --platform=node from the root `build` script: npm silently ignores flags passed after `--workspaces` that aren't recognized by `npm run`, so it had no effect (each package's own build script already sets --platform=node where esbuild needs it). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QMjKvi9vHT3LfikGfW84Kg * chore: add changeset Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QMjKvi9vHT3LfikGfW84Kg * ci,docs: post-merge fixes — drop Node 20, widen metadata range, sync docs-site CLI reference - Reconcile README with the merged Docusaurus docs site (#139): keep the monorepo intro/quick-start/development sections, point Documentation at metadata.jspsych.org and website/, drop the legacy docs/ links. - Drop Node 20 support (maintainer decision): engines >=22 in all three packages, release workflow bumped 20.x -> 22.x to match the CI matrix (22/24) that npm test actually runs on. - Widen the CLI's @jspsych/metadata range to '>=0.0.3 <0.2.0' so a future 0.0.x or 0.1.x patch release cannot re-break npm ci (caret ranges on 0.0.x match only that exact version). - Sync website/docs/reference/cli-reference.md with the exit-code scheme and flag-validation behavior that landed in #135 (the docs/ copy was updated there; the site copy predated it). - Resolve merge conflicts from main: take #136's DataUpload busy-state effect (webkitdirectory is now set via JSX spread, making #137's typed effect obsolete) and accept #136's deletion of global.d.ts. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
July 21, 2026 01:52
bb3afe0 to
e2e2f57
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
July 24, 2026 16:49
1ba29a8 to
a854654
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@jspsych/metadata-cli@0.2.0
@jspsych/metadata@0.1.0
frontend@0.1.0