Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Change bin/jsx default file extension to .jsx
See original GitHub issueCurrently, bin/jsx defaults to looking for .js files to which contain jsx content to compile. Whilst it’s possible to override this using jsx -x jsx ..., I think that since jsx content is not valid JavaScript, using the .js extension by default isn’t ideal.
Could we change bin/jsx to look for .jsx files instead?
Another advantage to this is that the generated .js files can live the same directory as the source .jsx. This simplifies the generation of source maps files as well, because the path to the .jsx is trivially relative to the generated .js
For example, given foo.jsx, running jsx . . would result in:
$ ls
foo.jsx
foo.js
foo.js.map
Issue Analytics
- State:
- Created 10 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Agreed on all points above. I’ll add that using
.jsxinstead of.jstips off your editor to highlight correctly.We’re deprecating react-tools so closing out.