i mean, you forgot to change the structure of this blog post when you ripped it off: <a href="https://www.stefanjudis.com/today-i-learned/prevent-npm-install-for-not-supported-node-js-versions/" rel="nofollow">https://www.stefanjudis.com/today-i-learned/prevent-npm-inst...</a> -- you also didn't change the title sufficiently, so if i search your title in google, i get stefan's post right under yours.<p>i also see that on your post just prior, you use an image that's stolen from this article: <a href="https://appuals.com/how-to-kill-process-on-port/" rel="nofollow">https://appuals.com/how-to-kill-process-on-port/</a><p>and of course, for that `kill-port` article here is the source you rewrote, which i found syndicated in a few different places:
- <a href="https://softbranchdevelopers.com/terminate-process-on-a-port-from-command-line/" rel="nofollow">https://softbranchdevelopers.com/terminate-process-on-a-port...</a><p>leaving aside that articles like these are basically just verbose refactors of official documentation, you could at least put in some effort. it's fine if you aren't original, but if you're just changing the phrasing of other people's articles and publishing that as your own work, for something as simple as `-prefers-color-scheme`, you're in the wrong field
Frequently enough, I find I need to ignore the `engines` property, since so many packages work in newer versions of node, but claim incompatibility. It’s well intentioned, but not very useful.