feat: support identifying jsxImportSource pragma dependencies #62
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.
Ref: denoland/deno#8440
This PR adds the following features:
@jsxImportSource
pragma from a modulejsx-runtime
(this is needed because when specifying "dev" mode, the implicit module name changes tojsx-dev-runtime
)This, plus the concept of "imports" already in the graph should allow us to support the React 17 JSX transforms in CLI (and in theory Deploy) in the least "hacky" way possible.
For context, something like this:
will get emitted to something like this:
And the parsing of the module would identify that
https://esm.sh/preact/jsx-runtime
would be what would be a runtime dependency and adds it to the dependencies of the graph module.