docs(core): document WASM parser async requirement #46
Conversation
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
Add JSDoc comment explaining that WASM-based synth parsers (v0.3.x) require parseAsync() and that sync parse() throws for tree-sitter based languages. This commit triggers a new release to publish the correct synth version constraints (^0.3.1) that were added in PR #44 but not published because 0.1.21 was already released from PR #43.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Add JSDoc comment explaining that WASM-based synth parsers (v0.3.x) require
parseAsync()and that syncparse()throws for tree-sitter based languages.This PR triggers a new release to publish the correct synth version constraints (
^0.3.1).Background
@sylphx/[email protected]at 11:44 UTC with OLD version constraints (^0.2.1)^0.3.1) but merged at 14:32 UTC (after chore(release): @sylphx/[email protected], @sylphx/[email protected] #43 published)The repo has correct versions but npm has the wrong ones. This PR will trigger 0.1.22 with the correct constraints.
Test plan
npm view @sylphx/[email protected] optionalDependenciesshows^0.3.1