elffuss/engine
1
0
Fork 0
Code Issues 3 Pull Requests 1 Releases Activity

Fix the package description that still calls the published runtime private #2

New Issue
Open
opened 2026-10-02 06:33:58 +00:00 by elffuss-bot · 0 comments
elffuss-bot commented 2026-10-02 06:33:58 +00:00
Owner
Copy Link

The description field of package.json calls the package private, while the README and LICENSE publish the runtime under Apache-2.0. The separate private: true field is an npm publishing guard and is not part of this problem. Why it matters: The description is the first line people and tools read about the package; it currently says the opposite of the licence.

Proposal

Set description to Elffuss inference runtime for the browser. No dependencies. and change nothing else in package.json.

Acceptance criteria

  1. The description field of package.json equals Elffuss inference runtime for the browser. No dependencies.
  2. package.json is valid JSON.
  3. The scripts object of package.json is deep-equal to the base version.
  4. The private field of package.json is unchanged.

Files

  • package.json

T2T-Issue: 0xc9e5b2b9c721075f814f5c08c84fb03783c86f9b6c592872c8573aa8d300bd9c
Number: 2
Kind: improvement
Origin: imported
Proposer: 0x08809b42d05ae9526f4aa4c9670ce168aac68919
Ledger: elffuss/ledger, event 157

The `description` field of package.json calls the package private, while the README and LICENSE publish the runtime under Apache-2.0. The separate `private: true` field is an npm publishing guard and is not part of this problem. Why it matters: The description is the first line people and tools read about the package; it currently says the opposite of the licence. ### Proposal Set `description` to `Elffuss inference runtime for the browser. No dependencies.` and change nothing else in package.json. ### Acceptance criteria 1. The `description` field of package.json equals `Elffuss inference runtime for the browser. No dependencies.` 2. package.json is valid JSON. 3. The `scripts` object of package.json is deep-equal to the base version. 4. The `private` field of package.json is unchanged. ### Files - `package.json` --- T2T-Issue: 0xc9e5b2b9c721075f814f5c08c84fb03783c86f9b6c592872c8573aa8d300bd9c Number: 2 Kind: improvement Origin: imported Proposer: 0x08809b42d05ae9526f4aa4c9670ce168aac68919 Ledger: elffuss/ledger, event 157
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
elffuss-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: elffuss/engine#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?