feat(analyze): add shared runtime target resolution#223
Open
dreyfus92 wants to merge 3 commits into
Open
Conversation
commit: |
|
| 📦 Package | 📋 Versions |
|---|---|
| @ast-grep/napi | 2 versions
|
| @ast-grep/napi-darwin-arm64 | 2 versions
|
| @ast-grep/napi-darwin-x64 | 2 versions
|
| @ast-grep/napi-linux-arm64-gnu | 2 versions
|
| @ast-grep/napi-linux-arm64-musl | 2 versions
|
| @ast-grep/napi-linux-x64-gnu | 2 versions
|
| @ast-grep/napi-linux-x64-musl | 2 versions
|
| @ast-grep/napi-win32-arm64-msvc | 2 versions
|
| @ast-grep/napi-win32-ia32-msvc | 2 versions
|
| @ast-grep/napi-win32-x64-msvc | 2 versions
|
| js-tokens | 2 versions
|
| semver | 3 versions
|
| make-dir | 2 versions
|
| eslint-visitor-keys | 2 versions
|
| balanced-match | 2 versions
|
| brace-expansion | 4 versions
|
| minimatch | 3 versions
|
| @humanwhocodes/retry | 2 versions
|
| ignore | 2 versions
|
| find-up | 2 versions
|
| locate-path | 2 versions
|
| picomatch | 2 versions
|
| p-limit | 2 versions
|
| p-locate | 2 versions
|
| path-exists | 2 versions
|
💡 To find out what depends on a specific package, run: npm ls example-package
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
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 PR adds the shared runtime target plumbing: there’s a small resolver that reads
--browserslist-query/--runtime, falls back to project Browserslist thenengines.node, and sticks the result onAnalysisContextfor later use. The actual checks (core-js, replacements, etc.) still behave like before we’re not switching them over yet.we also surface the resolved target in the analyze summary (and JSON stats) so it’s obvious what the run thought the target was, added browserslist as a real dependency, and covered the resolver with a few tests.
Note
also for some reason we had a duplicated
fast-wrap-ansiand I removed it.