Skip to content

fix: lowercase npm package name to @unabandoned/jsonstream - #4

Merged
00o-sh merged 1 commit into
masterfrom
claude/jsonstream-fork-repoint-nxxje5
Aug 14, 2026
Merged

fix: lowercase npm package name to @unabandoned/jsonstream#4
00o-sh merged 1 commit into
masterfrom
claude/jsonstream-fork-repoint-nxxje5

Conversation

@00o-sh

@00o-sh 00o-sh commented Aug 14, 2026

Copy link
Copy Markdown

Follow-up to #1. The onboarding merged with the package named @unabandoned/JSONStream, but npm forbids uppercase letters in new package names — that name can't be published, and it can't even be resolved as an npm: alias (npm fails name validation with "name can no longer contain capital letters", which is exactly what broke npm install in the first repoint PR).

This renames the published package to the lowercase @unabandoned/jsonstream.

What does not change:

  • The GitHub repo stays unabandoned/JSONStream.
  • Consumers keep the dependency key JSONStream, aliased to npm:@unabandoned/jsonstream@^1, so node_modules/JSONStream and require('JSONStream') are unchanged — no consumer code changes.
  • The JSONStream.parse / JSONStream.stringify API is untouched.

Also updates package in .unabandoned.yml to match (validated).

node --test test/*.js still passes (28/28) — the rename is inert to behaviour.


Generated by Claude Code

npm rejects capital letters in new package names, so "@unabandoned/JSONStream"
cannot be published (and cannot even be resolved as an npm: alias — it fails
name validation with "name can no longer contain capital letters"). Rename the
published package to the lowercase "@unabandoned/jsonstream".

Consumers keep the dependency key "JSONStream" (aliased to
npm:@unabandoned/jsonstream), so node_modules/JSONStream and require('JSONStream')
are unchanged. The GitHub repo name and the JSONStream.* API are unaffected.
@00o-sh
00o-sh merged commit 76dfce6 into master Aug 14, 2026
7 checks passed
@00o-sh
00o-sh deleted the claude/jsonstream-fork-repoint-nxxje5 branch August 14, 2026 12:54
00o-sh added a commit that referenced this pull request Aug 14, 2026
🤖 I have created a release *beep* *boop*
---


##
[1.4.0](jsonstream-v1.3.5...jsonstream-v1.4.0)
(2026-08-14)


### Features

* add option for emitting keys
([9aa2446](9aa2446))
* fork and onboard @unabandoned/JSONStream (vendor through, node:test
suite) ([#1](#1))
([f11ffef](f11ffef))


### Bug Fixes

* lowercase npm package name to @unabandoned/jsonstream
([#4](#4))
([76dfce6](76dfce6))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
00o-sh added a commit to unabandoned/deps-sort that referenced this pull request Aug 14, 2026
Repoints the `JSONStream` runtime dependency to
`npm:@unabandoned/jsonstream@^1`, so the abandoned upstream (and its
abandoned `through` dependency) leaves deps-sort' transitive tree. Part
of adopting JSONStream into the program — see unabandoned/JSONStream#1 /
unabandoned/JSONStream#4 and the tracking issue
unabandoned/browser-pack#3.

The dependency **key** stays `JSONStream` (aliased to
`npm:@unabandoned/jsonstream`), so `node_modules/JSONStream` and
`require('JSONStream')` are unchanged — the fork is a drop-in with the
same `JSONStream.parse` / `JSONStream.stringify` API, no code changes.

## Verification

Installed deps-sort's full tree with `@unabandoned/jsonstream` (packed
from the fork) standing in for the alias and ran the suite: **9 tests, 9
pass, 0 fail** on Node 22.22 and Node 24.19. `require('JSONStream')`
resolved to the fork.

## Ordering note

⚠️ **CI here stays red until `@unabandoned/jsonstream` is published to
npm** (unabandoned/JSONStream#4 → release → publish). `npm install`
can't resolve the alias until then; this is the expected
publish-ordering dependency, verified above via a local install of the
exact package contents. Holding ready-for-review in the meantime.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01Wa4Hra9ctCDzbpPUaQB9mG)_
00o-sh added a commit to unabandoned/insert-module-globals that referenced this pull request Aug 14, 2026
Repoints the `JSONStream` runtime dependency to
`npm:@unabandoned/jsonstream@^1`, so the abandoned upstream (and its
abandoned `through` dependency) leaves insert-module-globals' transitive
tree. Part of adopting JSONStream into the program — see
unabandoned/JSONStream#1 / unabandoned/JSONStream#4 and the tracking
issue unabandoned/browser-pack#3.

The dependency **key** stays `JSONStream` (aliased to
`npm:@unabandoned/jsonstream`), so `node_modules/JSONStream` and
`require('JSONStream')` are unchanged — the fork is a drop-in with the
same `JSONStream.parse` / `JSONStream.stringify` API, no code changes.

## Verification

Installed the full tree with `@unabandoned/jsonstream` (packed from the
fork) standing in for the alias and ran the suite: **17 pass, 0 fail, 1
skip** (the pre-existing `windows partitions` platform skip) on Node
22.22 and Node 24.19. `require('JSONStream')` resolved to the fork.

## Ordering note

⚠️ **CI here stays red until `@unabandoned/jsonstream` is published to
npm** (unabandoned/JSONStream#4 → release → publish). `npm install`
can't resolve the alias until then; this is the expected
publish-ordering dependency, verified above via a local install of the
exact package contents. Holding ready-for-review in the meantime.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01Wa4Hra9ctCDzbpPUaQB9mG)_
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