Renée

it doesn't have a `main` entry point specified in package.json, only an `exports` field. browserify doesn't support the newer `exports` field, but it also doesn't support ES modules, so the...

It's a slightly different issue. The OP is trying to use a package that probably fundamentally works in the browser, but browserify lacks support for ES modules, so it can't...

would like this but it's probably a significant effort! note that browserify's shims are all maintained separately so anyone could develop this and we could include it in browserify if...

Usually it's browser-pack-flat that causes incompatibilities. Try running it with `--no-flat`/`{flat: false}`: https://github.com/browserify/tinyify?tab=readme-ov-file#--no-flat-flat-false That's my only guess, would need to have an example that reproduces the issue to say any...

Per discussion in Slack, the JS QP already does this check, but the error gets mangled on the way up from deno to the final response. A fix for that...

I don't remember exactly but i think this is already done because of https://github.com/apollographql/federation-rs/pull/457, unless we hit some other error. new QP also fixes it.

The second response comes from the subgraph, meaning that in the router, validation did not reject the operation. But router and gateway both use the same JS validation implementation, so...

Wanna do one more apollo-federation release to **really** get this in order.

Filing a separate PR to change the default to `both` that we can land according to the release calendar, meanwhile this apollo-federation update can land now to support early experimentation...

Hmm, I still get test failures with this, for example with: ``` cargo run --test telemetry_test bad_query -- --nocapture ``` but that might be a second issue?