Migrate to exports #167
Closed
Migrate to exports #167
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sbatson5
force-pushed
the
migrate-to-exports
branch
from
1f66dd8
to
6d02609
Compare
sbatson5
force-pushed
the
migrate-to-exports
branch
from
a5cb7f8
to
82c02db
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR attempts to support both
importandrequiresyntax, following this blog post as a guide.This also updates a lot of dependencies that have gone out of date and should prepare use for migrating to firebase 9 and Typescript (although that will be a breaking/major change/release).
This also drops support for Node 10, 11 and 12, and adds support for 16, 17 and 18
Related issues
Fixes #144
How to test
Can someone point their repo to this branch and make sure it is backwards compatible with
requireand then works withimportsyntax?TODOs