Using peerDependency ranges that exclude future versions makes them useless and annoying. Sadly nobody is listening :(

Ricardo Amaral I would recommend to always use open ended ranges. E.g. "graphql": ">=14". Just like you would use `engines.node`. Basically only exclude what you know is broken and don't make guesses about the future.

📯 ProTip™: Use open ended ranges for "peerDependencies" in your package.json, just like you do for "engines" mobile.twitter.com/boennemann/sta…

🌟 10.000 stars on @GitHub 🌟 github.com/semantic-relea… Stephan Bönnemann-Walenta Gregor Matt Travi @pvdlg_

Massive TypeScript footgun. If you check for the existence of an optional enum parameter then the first value is falsey, because it's 0 under the hood. enum E {A, B} const fn = (i?: E) => { if (!i) alert('lol') } fn(E.A) // alerts That's stuff TS was supposed to prevent 🤔

Is there an npm@7 equivalent in yarn that would allow me to install all peerDependencies automatically? 🤔

It seems like there is not one day where I'm not stumbling over this: github.com/facebook/creat… x.com/SemanticReleas…

react-scripts with typescript causes an error on npm@7 install for months now, just because of a closed peerDependency definition ¯\_(ツ)_/¯ github.com/facebook/creat… x.com/boennemann/sta…

I'm starting to see a `node:` prefix for node core module imports pop up (VSCode inserts it, too), but I can't seem to find a write-up what this is about and where it's coming from. Does anyone have a pointer here? Should this be used now? Is there an ESLint rule to enforce etc?

As an... – iOS user I want to... – use a rolling date picker that defaults to today and blocks future dates, meaning I have to roll back the years before the date and month, on a device that is made to enter numbers via a numeric keypad so that... – I can provide my date of birth

Is there a freelance application monitoring expert to help me on a project? Looking at a focussed 4-6 weeks project. Structuring what we have, tooling advise, shipping something that we can confidently continue with. Berlin or remote (CEST±2).

Closed range peerDependencies should be impossible to publish to the npm registry without a force flag. This is such a massive waste of everyone's time.

“We introduced ‘Shape Up’ by Ryan Singer little over a year ago.” I’ve been hearing this more and more lately. There’s a lot of underground adoption and posts like this are the tip of the iceberg. linkedin.com/posts/boennema…