Skip to content
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
This repository was archived by the owner on Apr 22, 2023. It is now read-only.

Publish the current module to npm #328

Closed

Description

@bnb

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.

Activity

  1. zeke commented on Apr 29, 2020

    @zeke
    Contributor

    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.

  2. bnb commented on Apr 30, 2020

    @bnb
    Author

    cc @mhdawson @MylesBorins - do y'all know the correct avenue to getting something published under the @nodejs scope?

  3. Trott commented on Apr 22, 2023

    @Trott
    Member

    I've unarchived this repo so I can close all PRs and issues before re-archiving.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions