node-jsx
node-jsx copied to clipboard
petehunt
transparently require() jsx from within node
it is the best for ssr. i changed it for work with new jsx format where not need import react from react. but can it work with typescript? may be...
I intend on deprecating this repo in favor of https://babeljs.io/docs/usage/require/. If anyone has concerns about this please raise them here before I pull the trigger.
Added `require('node-jsx').install()` to my app and getting `Illegal return statement` when it tries to parse node libs under node_modules/. I'm guessing `{ extension: '.jsx' }` fixes it but I don't...
The following code: ``` js require('node-jsx').install(); var acorn = require('acorn'); ``` Results in: ``` /Users/forbeslindesay/Documents/GitHub/temp/node_modules/acorn/dist/acorn.js:2981 _classCallCheck(this, TokContext); ^ ReferenceError: TokContext is not defined at new TokContext (/Users/forbeslindesay/Documents/GitHub/temp/node_modules/acorn/dist/acorn.js:2981:25) at Object.15../state (/Users/forbeslindesay/Documents/GitHub/temp/node_modules/acorn/dist/acorn.js:2990:11)...
Is it a good idea to use `node-jsx` in production or better to pre-compile the files?
I know you may take it for granted and are seasoned at node + react, but on your main page can you explain the use case for this? I want...
specifying the type and URL is deprecated: https://docs.npmjs.com/files/package.json#license http://npm1k.org/
`node-jsx` works great! The only problem is when you have a big dependency tree where just a fraction of the files actually contain JSX. By defining paths... ``` js var...
I am building an isomorphic site using Fluxxor and React. Using node-jsx for the transforms and it works very well. Just having an issue though now as I have installed...
