Repository navigation
Say where Tabar is installed from - #9
Merged
Merged
Conversation
0.5.0 and 0.6.0 are published to GitHub Packages and nothing is on npm yet, so npm install needs a scoped .npmrc and a read:packages token, and the jsDelivr and unpkg links, which read npm, do not resolve yet. The README and docs/installation.md say so; docs/release.md says where releases go and why an old tag needs npm-release to publish.
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
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.
Tabar 0.5.0 and 0.6.0 are now published, to GitHub Packages (
PUBLISH_REGISTRY=github); nothing is on npm yet. The install docs still described an npm package:docs/installation.md:npm installneeds a scoped.npmrcand aread:packagestoken, now shown. A note above the CDN snippets says jsDelivr and unpkg read the npm registry, so those links resolve once Tabar is on npm; the snippets themselves are unchanged.docs/release.md: says where releases go today. It also notes that a tag push runsrelease.ymlas it was at the tagged commit, which is why the 0.5.0 and 0.6.0 tag runs tried npm and failed (ENEEDAUTH) and were published with.dev/tools/npm-release githubinstead.Docs only.