parcel-query tool #8478
Merged
parcel-query tool #8478
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
Benchmark ResultsKitchen Sink ✅
Timings
Cold Bundles
Cached BundlesNo bundle changes detected. React HackerNews ✅
Timings
Cold BundlesNo bundle changes detected. Cached BundlesNo bundle changes detected. AtlasKit Editor ✅
Timings
Cold BundlesNo bundle changes detected. Cached BundlesNo bundle changes detected. Three.js ✅
Timings
Cold BundlesNo bundle changes detected. Cached BundlesNo bundle changes detected. |
AGawrys
approved these changes
Dec 13, 2022
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.
Adds a CLI tool for inspecting the graphs stored in the Parcel cache (so notably, for doing analysis after a potentially long build without having to rebuild and adding some logging in a reporter somewhere).
(This is probably only marginally useful for end-users)
Some examples of what you can do:
.getAsset 3NkQQto figure out what asset is behind that public id.getAssetWithDependency <dependency id>,.getIncomingDependencies <asset>,.getResolvedAsset <dependency>,.findAsset <filepath regex>.findEntriesBundleGraph <asset>which doestraverseAncestors(so reverse DFS) and prints the “paths” or.findBundleReason <bundle-id> <asset-id>to hopefully say why that asset is in the bundlebundleGraphvariable and access the graph directly)Also exposes an API entrypoint do load the graphs in your own tooling (
loadGraphsgives you the asset, bundle, request graph and the bundle info).