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: improve and test importing web-ext as an ESM module or requiring as a CommonJS module #1934

Merged
merged 2 commits into from
Jul 14, 2020

Conversation

rpl
Copy link
Member

@rpl rpl commented Jun 18, 2020

This pull request contains a small set of proposed tweaks to improve a bit (and cover with tests) how web-ext can be used as a library, imported as an ESM module or required as a CommonJS module.

Given that this change what web-ext is going to export when loaded as a module, it would be likely better to be included in a major release (to avoid to break npm packages that may depend on the current exports).

Other pull requests related to this:

@coveralls
Copy link

coveralls commented Jun 18, 2020

Coverage Status

Coverage remained the same at 100.0% when pulling 9642ce9 on rpl:fix/importing-esm into 5badee6 on mozilla:master.

@rpl rpl requested a review from Rob--W June 18, 2020 14:53
@rpl
Copy link
Member Author

rpl commented Jun 18, 2020

@Rob--W no need to rush to review this, as I wrote in the description this isn't something that we should include in the upcoming v. 4.3.0 (I added it in the backlog of the next major release, v5.0.0), but I did pushed it so that we can evaluate this approach (and test coverage for this) in the meantime.

index.mjs Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants