develwoutacause’s Twitter Archive

25 results for npm

1. develwoutacause’s Twitter Archive—№ 1,338

   So apparently #NPM docs directly tell you to *check in* your NPM token. The motivation is for "using private packages", but this is *so easily misused* for new devs who

2. develwoutacause’s Twitter Archive—№ 699

   RT @dan_abramov: 📝 npm audit: Broken by Design https://overreacted.io/npm-audit-broken-by-design/ overreacted.io/npm-audit-broken-by-design/

3. develwoutacause’s Twitter Archive—№ 340

   run storybook fails with some missing dependencies. I had to npm install core-js concurrently --save-dev. The storybook script also references npm run build:ts, which just wasn't the convention I used,

4. develwoutacause’s Twitter Archive—№ 479

   outright missing files in node_modules/. It takes at least 5+ npm install or npm ci executions to get a successful install. Painfull.

5. develwoutacause’s Twitter Archive—№ 1,031

   #NPM feature request: npm deprecate-but-only-notify-direct-dependents Transitive dependents can't really do anything about a deprecation anyways and notifying them just causes a lot more panic and churn that it really should.