onchange 'src/**/*.{js,jsx}' -v -w -- babel-node src/index.jsx > dist/index.html
See original GitHub issueHow do you get the output of the command you want to run in a file?
onchange 'src/**/*.{js,jsx}' -v -w -- babel-node src/index.jsx > dist/index.html
The above will get the output from onchange
instead of babel-node src/index.jsx
Tried onchange 'src/**/*.{js,jsx}' -v -w -- (babel-node src/index.jsx > dist/index.html)
but gave me a error
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (3 by maintainers)
Top Results From Across the Web
React.js: Identifying different inputs with one onChange handler
I suggest sticking to standard HTML attributes like name on input Elements to identify your inputs. Also, you don't need to keep "total"...
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
I understand that, but I was asking @gertcuykens what his use-case was and what exactly wasn’t working. It wasn’t clear from the original post whether literally nothing worked, or it just didn’t work as expected. For example, the output of
onchange
should be identical tobabel-node
, which is why I asked for more info.On the
-o
feature, I love it and would love to add it. I definitely don’t have a problem with it and understand the use-case.@gertcuykens if it’s a node app you can also use npm scripts instead of creating a separate file