Use of source.jsx scope for react
See original GitHub issueLooks like ST4 now supports a scope: source.jsx
for JSX containing files. It mainly sets up a custom jsx file icon. Should the react JSCustom config start using that scope instead?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
'React' must be in scope when using JSX ... - Stack Overflow
Whenever we make a custom component in React using JSX, it is transformed into backward-compatible JS code with the ...
Read more >Why do React need to be in scope for JSX - DEV Community
Exactly : React must be in scope when using JSX . If we don't import it at the top of our file, the...
Read more >eslint-plugin-react/react-in-jsx-scope.md at master - GitHub
When using JSX, <a /> expands to React.createElement("a") . Therefore the React variable must be in scope. If you are using the @jsx...
Read more >Must React Be in Scope When Using JSX? - Upmostly
When you use JSX, the compiler transforms it into React function calls that the browser can understand. The old JSX transform turned JSX...
Read more >Introducing the New JSX Transform – React Blog
What's Different in the New Transform? · Because JSX was compiled into React.createElement , React needed to be in scope if you used...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s not deep-merged, no; if you want the example configurations plus changes, you’ll have to copy the
configurations
object and modify it.I’ve set the react syntax to the jsx scope, and things are working great (though I did have to modify some scopes on other plugins to get them to activate in the new jsx scope.
Closing for now, reopen if you feel there is more to do here. Perhaps in the future this can be made to be the default.