Do you happen to use an NPM proxy? We discussed in #137 how to fix that.

Other than that I have not enough info about your environment to guess the cause. However, it is most likely about the support of scoped packages. Maybe that helps you with further googling... Let me know if you have more to tell!

Hi,
I have the same problem here. It's working perfectly on my local machine, but when I try to install it through a Dokerfile I have the 404 error

In my Dockerfile I tried to call like this :

FROM readytalk/nodejs

WORKDIR /home/nodeapp
ADD package.json /home/nodeapp
RUN npm config set "@request:registry" https://registry.npmjs.org/
RUN npm install
ADD . /home/nodeapp

EXPOSE 8080
CMD ["node","server.js"]

And in my package.json I have these dependencies :

"dependencies": {
"async": "^2.0.1",
"body-parser": "^1.15.2",
"express": "^4.14.0",
"request": "^2.74.0",
"request-promise": "^4.1.0"
}

But I always have the 404 error.

I just published [email protected] which fixes this issue for good.

The number of bug reports in this issue and elsewhere piled up way too high so I renamed @request/promise-core to request-promise-core. Sorry guys, I didn't anticipate that scoped packages produce that much hassle...

No problem, thanks a lot! ;)

@analog-nico
I'm new to nodejs, I try to npm install parse-server, but I have this error Invalid name: "@request/promise-core", do you know how I can fix it?

@xinsamwan Just upgrade to request-promise to version 4.1.1.