Hyeseong Kim

Of course, simplicity is important, but there is another big problem here. Adding personal opinions without esbuild config already existing or well-known standards is against the goal of the nanobundle....

I have an strategy for this and have done some PoCs. I have to investigate more for compatibility with watch mode, but I believe I can begin late this month.

This will need native stuff and esy configuration. But I can support :)

I see many contributors constantly mentioning binding style. It won't be zero-cost bindings, regardless of whether or not we use functors. I'm willing to accept additional runtime to fit the...

That's is easy if we can run the printer standalone. Or, it would be ideal to publish to NPM and directly use its WASM or NAPI distribution

Workaround: Commit md5 hashes for all the fixtures in the graphql-text-printer crate test suite. Then we can compare it when running the babel plugin tests.

@captbaritone I added idempotency testing using compiler-side fixtures. Fixed 4 failures related to spaces between multiple definitions and it all passes.

I think it makes more sense for each package to have a lockfile since there is no workspaces setup, or gitignoring. `yarn install` is needed to run the test suite...

setup here? or another pr?

https://github.com/facebook/relay/pull/4711 I'm not sure it could actually boost the CI, let's see.