Module ESM Conversion - #96
Merged
Merged
Conversation
…nversion # Conflicts: # package.json
# Conflicts: # AppBuilder # package.json
…nversion # Conflicts: # AppBuilder # package.json
johnny-hausman
added
the
minor
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updating our codebase to use ESM import formats rather than the previous require() statements.
This PR will depend on the corresponding AppBuilder ( PR ) and Core ( PR ) commits being in place.
These Commits will not test properly until all the pieces are in place, so I will start at the Upper level services and force commit them, until we are finally down to the Core repo. Then that one should have access to all the pieces already being in place and successfully commit. The GitHub updating tools will then update all the upper repos as a result.
That's the theory.