This is some sort of answer to recent posts regarding Web Components, where more than a few misconceptions were delivered as fact.
Let's start by defining what we are talking about.
As you can read in the dedicated GitHub page, Web Components is a group of features, where each feature works already by itself, and it doesn't need other features of the group to be already usable, or useful.
| (async function generateReplies(document) { | |
| // https://conventionalcomments.org/#labels | |
| const LABEL = { | |
| praise: "praise", | |
| nitpick: "nitpick", | |
| suggestion: "suggestion", | |
| issue: "issue", | |
| todo: "todo", | |
| question: "question", | |
| thought: "thought", |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).
You can add all conventional comments Labels to Github as a saved replies by following the following steps:
- Go to https://github.com/settings/replies
- Open Developer Tools
- Copy/Paste above code in JavaScript console
- Press enter
Winds up being a (not the) rather comprehensive JavaScript toolbox. The idea being for the modern JavaScript programmer can use all of the tools available for a given requirement, task or job, without preference for any. No external bundlers or
compilers are needed. No frameworks are needed. I can use qjs or tjs for systems
with minimal RAM and disk space; and when I want to use Web API's deno makes an effort
to provide those interfaces. In some cases I can run the exact same code in bun, deno, and node,
which provides a means to perform 1:1 testing as to performance.
There's probably a few things I am unintentionally omitting below. These are just a brief synposis. I'll update accordingly.