
Research
SANDWORM_MODE: Shai-Hulud-Style npm Worm Hijacks CI Workflows and Poisons AI Toolchains
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.
Break out of a promise chain
This is an experiment. I personally wouldn't recommend this.
Feedback wanted on the issue tracker.
See "How do I break out of a promise chain?" for a better way.
$ npm install --save p-break
Here the onlyRunConditional promises are skipped if conditional is falsy:
const pBreak = require('p-break');
alwaysRun1()
.then(() => alwaysRun2())
.then(conditional => conditional || pBreak('🦄'))
.then(() => onlyRunConditional1())
.then(() => onlyRunConditional2())
.then(() => onlyRunConditional3())
.then(() => onlyRunConditional4())
.catch(pBreak.end)
.then(console.log);
//=> '🦄'
Starts the break. Any .then()'s between here and pBreak.end() are skipped.
Value to pass down the chain after pBreak.end().
Ends the break. Make sure not to have any other .catch() handlers between pBreak() and here.
MIT © Sindre Sorhus
FAQs
Break out of a promise chain
We found that p-break demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.

Company News
Socket is proud to join the OpenJS Foundation as a Silver Member, deepening our commitment to the long-term health and security of the JavaScript ecosystem.

Security News
npm now links to Socket's security analysis on every package page. Here's what you'll find when you click through.