Peter Donald

Ooer - that does sound like an interesting idea. One thing I have been contemplating lately is somehow injecting other sources of metadata into the generation pipeline. In particular I...

...snip... > DomGlobal.hasFeature("my.new.feature") That is certainly a better place than where we are now and would probably work in most cases.

> The initial version of the jsinterop-generator was using WebIDL as input instead of extern files and we gave up. Interesting. > * the type defintion in WebIdl does not...

I would love to see a java constant added for this name such as `JsType.GLOBAL` with a little comment to indicate what it does. Although then we have both `JsType.GLOBAL`...

I guess that may be true in the google context where everything is built from source and the project that defines the artifact is also responsible for defining the blaze/bazel...

In this particular use case the `braincheck` library is an invariant checking library that is completely optimized away in production builds. In GWT terms, the debugger statement is only really...

@rluble I am guessing that the above use case did not make the grade? :) Another scenario where I want to use it is to make it easier to share...

At the risk of sounding like a bit me-too. This kind of direction would definitely appeal to us. We currently are relatively heavily invested into dagger for our client-side apps...

A good article gives an overview of options - [React Animation Libraries for 2020](https://blog.bitsrc.io/react-animation-libraries-for-2020-437a21c73fed)

Some (somewhat dated) links from when we originally wanted to go down this path: - [react-simple-animate](https://react-simple-animate.now.sh/) (Seems like the best easy option) - [react-animation](https://www.npmjs.com/package/@nearform/react-animation) - [pose](https://popmotion.io/pose/)