This is why I specify peer dependency ranges as >=. What are the odds a Vite plugin will break in Vite 9, 10, or 11?

Maybe people want to disallow the use of CJS syntax?

It’s just a guess. Personally I recommend using "preserve".

I also really like Mr. Pickles and Metalocalypse, but you may need to be a metalhead to appreciate those, especially Metalocalypse.

I don’t mind violence and gore as long as it’s not real. I’ll check out Dorohedoro, but also some people decided to release new seasons of Daredevil, Maul, Invincible, and the Boys simultaneously. So much to watch!

Yes! Those are amazing! I also think Amphibia belongs on that list.

I absolutely loved Blue Eye Samurai and Hilda 😄

Oh yeah, I definitely agree with that.

I like it when you share that kind of stuff. It shows that you’re a real person with interests besides programming. I’m not personally into these specific topics, so I’m not really inclined to engage.

I definitely watched some cool TV series because you shared them.

`process` also has a browser polyfill. You don’t need it in Node.js, but it makes sense if this is a transitive dependency.

It is over 9 years old now though. There are better ways now to define a polyfill for this using package exports.

They are proprietary 🙁

What would you like to test?

Bonus points if you register it in the JSON Schema Store.

Does it also support syntax extensions? (frontmatter, gfm, directives, etc)

This particular example seems wrong though?

I stand by my opinion that it’s better to use yaml instead of js-yaml. This has to do with spec compliancy though, not performance. When it comes to performance, people have pointed out js-yaml is faster.

Does anyone know how to disable that “Ask Google” button in the Google Chrome omnibar? I don’t use it, and it annoys me.

Thanks to whoever worked on this! 💖

a screenshot of the npmjs.com package page with a dark button in the header highlighted

dark mode on www.npmjs.com ???

Docusaurus 3.10 | Docusaurus We are happy to announce Docusaurus 3.10.

💥 Docusaurus 3.10 is out!

Milestone release - Prepare for Docusaurus 4

🔐 Security: Trusted Publishing, CI scanner, recommendations
⚡ Docusaurus Faster - Stable, soon the new default
💪 Strict MDX - No proprietary syntax
💾 Storage API - Stable
🌳 VCS API - Experimental

docusaurus.io/blog/release...

Did you know both also support an optional title inside the curl? Titul? Titearl?

[alt](url "title")

I like that source maps are local. The same arguments could be made about type declarations.

> the package you publish to npm shouldn't contain sourcemaps

That’s just an opinion though. I do ship sourcemaps with my packages.

This already happens if sourceMappingURL comments are used. What are you missing?

Another reason the world should change to the Canadian date-time notation

The GitHub security and quality side menu, listing: Dependabot, Malware, Vulnerabilities, Code scanning, Secret scanning, Security policy, and Advisories.

This distinction between malware and vulnerabilities in the GitHub security tab is new, isn’t it? It’s a good distinction.

`never` and `unknown` represent concepts that actually exist in JS.

What else does a function return that always throws? And what if a function accepts any value as input?

The JavaScript `void` keyword is unrelated here, but the name equivalence is confusing.

In case of a callback, the callee determines what’s allowed. “I” and “you” are the same person here.

In case of a function, why would you observe a constant return value of undefined?

A `never` return type means it has to throw. So the statement after such a function call is considered unreachable.

You may want to run code after calling a callback.

But it does end up there, because types get transformed in all sorts of ways.

A common example is the `resolve` function in the `Promise<void>` constructor callback.

There are absolutely pros and cons. Malicious lockfiles can be crafted. I delete lockfiles and inspect package.json before for example trying a reproduction repo. It’s also dangerous to accept PRs with lockfile changes.

And yes, I do use lockfiles for my own projects.

Its meaning is use case dependant. For callbacks, indeed, use unknown instead. You can also use it in type annotations for variables or arguments.

It represents something that doesn’t exist in JavaScript. A function without an explicit return value, returns undefined, not void. This mismatch causes all sorts of weird issues.