NPM proxy users receiving ERR 418 I'm a teapot

Re:NPM proxy users receiving ERR 418 I'm a teapot by xab9 on Tuesday May 29, 2018 @01:51PM (#17181422)

`npm i` breaks. Then we delete the lock file (and usually node_modules), run npm i again and it works. Probably it works for you and we are just unlucky or we were too lazy to use some cli magic, dunno. Yarn people here (at the company) usually say that yarn worked for them better, can't clarify about that.

One time out of fun and curiosity we flushed the cache and deleted the lockfile and the node modules dir, did npm i on a mac and a windows and they were undiffably different. Okay, this was months ago and probably there is a good explanation for it, but it was not reassuring.

[ Parent | on HN ]

Re:NPM proxy users receiving ERR 418 I'm a teapot by abritinthebay on Thursday May 31, 2018 @02:50PM (#17198958)

Yarn breaks things all the time for me. Practically every build process issue I’ve had in the last 7 months has been Yarn related.

Never had `npm i` break though... does it fail if you do `npm ci`? Are you pinning versions? Very peculiar behavior.

[ Parent | on HN ]

Re:NPM proxy users receiving ERR 418 I'm a teapot by xab9 on Friday June 01, 2018 @02:15AM (#17202989)

Didn't try it, but I will, thanks.

[ Parent | on HN ]