app tree resolving #1373
Merged
app tree resolving #1373
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
This supersedes #1357 now that we've landed several prerequisites and can do it properly in one shot. First step here is to implement app-tree resolving module-resolver.
Closed
…he modules don't move their on-disk locations
ef4
force-pushed
the
app-tree-resolving2
branch
from
bdb94be
to
267eee9
Compare
|
Latest note-to-self here: the latest commit streamlined how entry points get built but that is going to cause several tests to need to be updated, where the tests were making assumptions about the entrypoint formatting. |
This was referenced May 2, 2023
Closed
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.
This supersedes #1357 now that we've landed several prerequisites and can do it properly in one shot.
First step here is to implement app-tree resolving module-resolver.