-
-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jsxRuntimeImport not getting picked up? #801
Comments
Looks like this might need even more work, because the hyperapp integration expects
where the existing code only seems to support
D: |
shish
added a commit
to shish/svgr
that referenced
this issue
Nov 28, 2022
I need to have a config which isn't currently supported
shish
added a commit
to shish/svgr
that referenced
this issue
Nov 28, 2022
…#801 `hyperapp-jsx-pragma` uses the default export so we need to `import h from "hyperapp-jsx-pragma"`, not `import { h } from "hyperapp-jsx-pragma"`
shish
added a commit
to shish/svgr
that referenced
this issue
Nov 29, 2022
…#801 `hyperapp-jsx-pragma` uses the default export so we need to `import h from "hyperapp-jsx-pragma"`, not `import { h } from "hyperapp-jsx-pragma"`
shish
added a commit
to shish/svgr
that referenced
this issue
Nov 29, 2022
I need to have a config which isn't currently supported
shish
added a commit
to shish/svgr
that referenced
this issue
Nov 29, 2022
…#801 `hyperapp-jsx-pragma` uses the default export so we need to `import h from "hyperapp-jsx-pragma"`, not `import { h } from "hyperapp-jsx-pragma"`
shish
added a commit
to shish/svgr
that referenced
this issue
Nov 29, 2022
…#801 `hyperapp-jsx-pragma` uses the default export so we need to `import h from "hyperapp-jsx-pragma"`, not `import { h } from "hyperapp-jsx-pragma"`
shish
added a commit
to shish/svgr
that referenced
this issue
Nov 29, 2022
…#801 `hyperapp-jsx-pragma` uses the default export so we need to `import h from "hyperapp-jsx-pragma"`, not `import { h } from "hyperapp-jsx-pragma"`
+1 |
1 similar comment
+1 |
gregberge
pushed a commit
that referenced
this issue
Mar 14, 2023
* Allow specifying `jsxRuntimeImport` in config, see #801 I need to have a config which isn't currently supported * Allow specifying a single specifier for custom imports, see #801 `hyperapp-jsx-pragma` uses the default export so we need to `import h from "hyperapp-jsx-pragma"`, not `import { h } from "hyperapp-jsx-pragma"`
Fixed in 86bb86f |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I have this in my package.json, the output is changed appropriately:
But this seems to have no effect :(
(I need to use the custom version because I'm using HyperApp as a framework, and so I need my
h
to be imported from thehyperapp-jsx-pragma
package)The text was updated successfully, but these errors were encountered: