Cameron Martin

Am I correct in thinking this should be solved in 0.5? I am using 0.5.1 and still encountering this, should I raise a bug?

Is there anything preventing this over upgrading the dependency versions?

At least two of the things that are blocking are: * [This repo needs to fully replace react-motion with react-spring](https://github.com/plouc/nivo/issues/667) * [react-spring needs to support React 18](https://github.com/pmndrs/react-spring/issues/1563)

Upgrading the whole repo to use React 18 isn't trivial, because storybook needs upgrading to a version that supports React 18. However, this requires replacing the deprecated `@storybook/addon-info` and `@storybook/addon-knobs`....

> Actually, the code above is obsolete. This is in the version used by the latest stable version of react-bootstrap. Would you consider releasing a patch for this on that...

This could be fixed by using a different identifier for reserved words and renaming the export, e.g: ```ts const _default: string; export { _default as default }; ```

The [docs for Language Service Plugins](https://github.com/Microsoft/TypeScript/wiki/Writing-a-Language-Service-Plugin) suggests that this wouldn't work > TypeScript Language Service Plugins ("plugins") are for changing the editing experience only. The core TypeScript language remains the...

That was me starting to mess around with Typescript language service plugins (with the aim to create one for CSS modules). I didn't get very far though :(

I believe this is due to the distinction between _global config_ and _project config_. Properties that come from the global config are only valid at the top level, whereas properties...

This makes sense. I think it is a blocker for rules_rust adopting bzlmod, since I don't think all the toolchains could easily be defined in one repository. I can take...