Install private packages locally with SSH authentication instead of PAT

[Spielboerg]

Currently it is only possible to install private packages from Github Packages with a PAT: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#authenticating-to-github-packages

It would be great if not all developers had to create a PAT just to install the package, but could just use the already existing SSH authentication.

[ankit-toddleapp]

Is there any update on this!?

[pranavq212]

still looking for this, any updates?

[mr-rpl]

+1

[shankar-ccm]

I have github packages in my company private github account and I want to install those packages in another project using dependency in package.json and npm.

Below are the steps I am following.

created .npmrc file
registry=https://registry.npmjs.org/
@{scope}:registry=https://npm.pkg.github.com/
//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}

added dependecy in package.json
"@{scope}/name": "1.0.3",

created PAT for organization

npm install in github action

name: Install Dependencies
run: |
npm cache clean --force
npm install
env:
NODE_AUTH_TOKEN: ${{ secrets.PAT_TOKEN }}
but I am getting 404 error like below

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@{scope}%2fname - Not found
npm ERR! 404
npm ERR! 404 '@{scope}/name@1.0.3' is not in this registry.

any suggestions or solutions are appreciated.

[Spielboerg]

I'm using the setup node action instead of a .npmrc file:

steps:
  - name: Check out latest repository code
    uses: actions/checkout@v3

  - name: Setup node
    uses: actions/setup-node@v3
    with:
      node-version: 16
      registry-url: 'https://npm.pkg.github.com'
      scope: '@{scope}'

  - name: Install dependencies
    run: npm ci
    env:
      NODE_AUTH_TOKEN: ${{ secrets.PAT_TOKEN }}

---

Note: @{scope} is a placeholder and must be replaced with the name of your organization, e.g. @my-org.

[mycarrysun]

I'm not sure if @{scope} is in a documentation page somewhere or not but that's not correct. You should replace that with the name of your org on github. For example @cool-org would be for an org called cool-org.

[mycarrysun]

Also this issue is not related to your problem - but hope that fixes it for you.

[Spielboerg]

I'm not sure if @{scope} is in a documentation page somewhere or not but that's not correct. You should replace that with the name of your org on github. For example @cool-org would be for an org called cool-org.

I just assumed that @shankar-ccm used it as a placeholder, and I adopted that. I have now added a note above to make it immediately understandable for future readers.

[mycarrysun]

Oh yea I didn't realize I was replying to a different person 😅 @shankar-ccm the issue should be fixed if you use the org name instead of @{scope}

[nickfujita]

+1
Having to explain to an entire org that wants to use private packages that in addition to their ssh key, that already grants them access to private repos, they now have to add a new PAT, is a small, but seemingly unnecessary hurdle.