Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

189
Views
Private NPM package missing folders after global install

I've created an published an NPM package successfully to our private Verdaccio instance. Following a global install from our private NPM registry we are missing the src/ and test/ sub-directories.

There is nothing referenced in the .npmignore or .gitignore files, and we are even explicitly referencing the src/ sub-directory in files block in the package.json:

Package JSON

{
...
  "main": "./bin/cli.js",
  "bin": {
    "app_name": "./bin/cli.js"
  },
  "scripts": {
    "start": "node ./bin/cli.js"
  },
  "files": [
    "bin",
    "test",
    "src",
    "package.json"
  ],
...
}

I've tried the following to resolve but no luck:

  • Moving the cli.js in to the src sub-dir.
  • Explicitly listing the src and test sub-dir within the files block in the package.json (strangely this is working and ignores other directories, it just never installs the src and test sub-dir.)

Moving the entry point to the src/ sub-directory results in it failing to install at all with the following error:

ENOENT: no such file or directory, chmod '...node_modules/@private_registry/app_name/src/cli.js

I don't think there is an issue with the publish, as I can pull down the tarball and extract the src and test sub-directories.

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!