Patrik Oldsberg

Regarding the ability to override components with ones from your own design system, this is not something that we currently expect to be able to provide as a feature of...

Gonna close as fixed by #26873, let's handle other potential bugs in new issues

It's not a huge priority at the moment, but we're taking steps towards it. Most recently we added support for the `exports` field in #15816. I think it's best to...

@JounQin Any package can provide both ESM and CJS implementations, if they are only compatible with ESM then that is because they chose to not provide CJS support to their...

@JounQin yep but ESM doesn't replace CJS, the intention is for both of them to exist as complementary module systems in Node.js. We'll add support for ESM so that we...

I've dug into this some more again and reached a few conclusions that I'd like some feedback on: In order to support ESM in backend code we need to add...

@jonkoops [wooorm/npm-esm-vs-cjs](https://github.com/wooorm/npm-esm-vs-cjs) looks interesting! Only analyzing `latest` seems a bit tricky though, since splitting CJS/ESM support across version seems like a fairly common approach. Another example that might be more...

Hi! This is actually already a built-in feature of GitHub project workflows:

Are you seeing any errors if you run `yarn tsc`? Another thing to check for is that the `node_modules/@backstage/plugin-kubernetes-backend` folder seems correct, i.e. that it contains a `package.json` with an...

Huh, that is new, probably something on the docker side 🤔