saas-boilerplate icon indicating copy to clipboard operation
saas-boilerplate copied to clipboard

 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@sb%2Finfra-core: Not Found - 404

Open tribanos opened this issue 4 months ago • 1 comments

Describe the bug

I cant install the boilerplate. After pnpm install i get this error: " ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@sb%2Finfra-core: Not Found - 404"

Checked it in npmjs explorer and didnt find it.

Steps to reproduce

(ubuntu 22.04)

  1. wget latest boilerplate release
  2. tar xvfz..
  3. cd into extracted folder
  4. run command: pnpm install

System Info

System:
    OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
    Memory: 14.57 GB / 15.59 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.12.2 - /usr/bin/node
    npm: 10.5.0 - /usr/bin/npm
    pnpm: 9.0.4 - /usr/local/bin/pnpm

Logs

Click to see log!
pnpm install
packages/webapp                          |  WARN  The field "pnpm" was found in /home/podcraft/saas-boilerplate-2.6.0/packages/webapp/package.json. This will not take effect. You should configure "pnpm" at the root of the workspace instead.
Scope: all 22 workspace projects
/home/podcraft/saas-boilerplate-2.6.0/packages/backend:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@sb%2Finfra-core: Not Found - 404

This error happened while installing a direct dependency of /home/podcraft/saas-boilerplate-2.6.0/packages/backend

@sb/infra-core is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.
Progress: resolved 7, reused 7, downloaded 0, added 0

Validations

tribanos avatar Apr 21 '24 08:04 tribanos

Your steps to reproduce are not supposed to work, you are missing the step to initialize the boilerplate:

pnpm create saas-boilerplate PATH

You should follow https://docs.demo.saas.apptoku.com/getting-started/run-project/run-new-project

gabrii avatar Apr 21 '24 09:04 gabrii

This is caused by the pnpm v9. Latest released version is not backward compatible and until we fix this I recommend to use pnpm 8

mkleszcz avatar May 06 '24 07:05 mkleszcz