You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
Currently the npm package instructions require installation from GitHub.
I'd like to see this module published to GitHub within the Node.js scope. Given the repo name and the module purpose, I think @nodejs/i18n is appropriate? Open to suggestions but I think it's a reasonable scope.
I'm not sure who controls the @nodejs scope, but if publishing to that scope is reasonable to y'all we can ping a few folks who will know.
Having test-driven the GitHub-hosted module, I've already run into a few snags. In my case, I was unable to install the module in a GitHub Action because I was using a node-alpine container image. Took me a while to figure out that those images don't include git, and that git is what's used by npm under the hood to install GitHub-based dependencies.
I'd be happy to help set this up once we land on a package name. If we can use the @nodejs scope and name it @nodejs/i18n, I think that would be great.
Reacted by Tierney Cyren, Tiago Danin and Dhruv Jain
Activity
zeke commentedon Apr 29, 2020
Having test-driven the GitHub-hosted module, I've already run into a few snags. In my case, I was unable to install the module in a GitHub Action because I was using a node-alpine container image. Took me a while to figure out that those images don't include
git, and that git is what's used bynpmunder the hood to install GitHub-based dependencies.I'd be happy to help set this up once we land on a package name. If we can use the
@nodejsscope and name it@nodejs/i18n, I think that would be great.bnb commentedon Apr 30, 2020
cc @mhdawson @MylesBorins - do y'all know the correct avenue to getting something published under the
@nodejsscope?Trott commentedon Apr 22, 2023
I've unarchived this repo so I can close all PRs and issues before re-archiving.