feat: rename npm package prefix to @plmbr#342
Merged
Conversation
pjdoland
added a commit
to pjdoland/notebook-intelligence
that referenced
this pull request
May 23, 2026
The notebook-intelligence org was renamed to plmbr, and the npm package scope renamed from @notebook-intelligence/notebook-intelligence to @plmbr/notebook-intelligence (plmbr#342). GitHub redirects the old URLs, but every page on plmbr.dev still rendered with the pre-rename org name in headers, footers, layouts, posts, and content pages, and the install checklist still pointed at the old npm scope. This points 22 files at the new canonical `github.com/plmbr/notebook-intelligence` shape and updates the labextension checklist entry to match the live npm name. Scope intentionally excludes `_config.yml`'s url / baseurl / domain block and CNAME, both already updated upstream in the recent domain-cutover commits.
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.
No description provided.