Skip to content

TypeScript packages: version 0.1.0, one npm workspace, install from this repository - #9

Merged
JoshuaWink merged 3 commits into
betafrom
npm-beta
Oct 10, 2026
Merged

JoshuaWink merged 3 commits into
betafrom
npm-beta

Conversation

@JoshuaWink

@JoshuaWink JoshuaWink commented Oct 10, 2026 •

Copy link
Copy Markdown
Member

What changes

  • The three TypeScript packages are version 0.1.0. A version below 1.0 says that a package is not stable yet. (The pull request before this one in the stack set 1.0.0-beta.1; this one replaces it.)
  • The packages are one npm workspace, with one lock file at the root of the repository.
  • codeupipe-lint and codeupipe-compile need the exact version of codeupipe, so that the packages can be packed and installed.
  • The packages stay private and are not on npm. The README says how to make them from this repository with npm pack and install the files.
  • The core package has no rule for the Node version. The two tools need Node 20.
  • CI has one job for the TypeScript packages.

Checked

The three files that npm pack makes were installed in a new project with the commands of the README. The library, codeupipe-lint and codeupipe-compile ran from the installed copies.

This pull request is the last of a stack. Merge the stack in order, with a merge commit.

🤖 Generated with Claude Code

JoshuaWink and others added 2 commits October 10, 2026 15:58
- The packages are no longer private. Each one publishes with the npm
  tag "beta", so a person gets it with npm install codeupipe@beta.
- The three packages are one npm workspace, with one lock file at the
  root of the repository. codeupipe-lint and codeupipe-compile need the
  exact version of codeupipe, where they had a link to its directory.
- The built core package has no rule for the Node version: its
  JavaScript runs in a browser and in older Node. The two tools need
  Node 20.
- CI has one job for the TypeScript packages, and it also makes the
  packages as npm does.

Nothing is published by this change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A version below 1.0 says that the packages are not stable yet. They
publish with the normal npm tag, so npm install codeupipe gives them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JoshuaWink JoshuaWink changed the title The TypeScript packages can go to npm, as a beta The TypeScript packages can go to npm, as version 0.1.0 Oct 10, 2026
The packages are private again, so that a publish cannot happen by
accident. The README says how to make them from this repository and
install the files that npm pack writes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JoshuaWink JoshuaWink changed the title The TypeScript packages can go to npm, as version 0.1.0 TypeScript packages: version 0.1.0, one npm workspace, install from this repository Oct 10, 2026
@JoshuaWink
JoshuaWink changed the base branch from version-2-beta to beta October 10, 2026 21:19
@JoshuaWink
JoshuaWink merged commit 810f39c into beta Oct 10, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant