Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(esbuild): provide JSModuleInfo of output bundle #2685

Merged
merged 1 commit into from
May 20, 2021

Conversation

jbedard
Copy link
Collaborator

@jbedard jbedard commented May 18, 2021

Seems like other rules such as rollup and terser provide this, and it makes sense. I'm not sure of the greatest way to test it though? All 3 could probably use such a test...

@mattem
Copy link
Collaborator

mattem commented May 20, 2021

Seems good to me, even with a test I'm not sure exactly what we'd be testing, as at this point handling providers is bazel internal, there is no starlark logic here and we have existing tests to verify the right output.

@mattem mattem merged commit 233254d into bazel-contrib:stable May 20, 2021
@jbedard
Copy link
Collaborator Author

jbedard commented May 20, 2021

I think a test would need to confirm that the provider interacts with another rule consuming the provider and make sure the integrate properly. However most rules consuming this provider fallback to the default info anyway so the tests would probably pass either way >_>

I still think it's worth the consistency with rollup+terser etc 🤷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants