Seivan

Sorry, but `process.env.NODE_ENV` is somewhat of a standard. You don't want to encourage the use of the one key that almost every project, including React and Vite uses?

That's beyond the point. Vite is using `process.env.NODE_ENV` internally. [React](https://github.com/facebook/react/search?q=NODE_ENV) is using it. Every single library you got... is using it. You can make the claim that `import.meta.env` will eventually...

Notes: - [ ] TSConfing `"jsx": "react"` is opt out of automatic runtime. - [ ] TSConfig defined `"jsxImportSource": "react"` is default to current settings. - [ ] Anything else,...

All the heavy lifting is already done by the React plugin, this is purely a convenience feature. Making sure that we don't repeat configs and keep one single source of...

Depends on this https://github.com/TimNN/cargo-lipo/issues/26

@Lokathor Fat chance, Android is no mans land.

+1 on this. Makes it easier to purge cache as well. Or the ability to define a method that generates keys in config so people could override it. EDIT; Saw...

It's alright I'm actually switching to the CLI with the options defined here to be backwards compatible anyway.

I get this as well. Only one file (notice no semicolons) ``` typescript class Greeter { greeting: T constructor(message: T) { this.greeting = message } greet() { return this.greeting }...

So is blocks the only way? the delegate methods from the Examples do not seem to work.