Hacker News Reader

Comment by nexuist | Hacker News Reader

> It's crazy to me that it's normal now to have like 3-4 compilation/transpilation steps when working on a simple JS-based app.

This is why I stick with Vue. One <script> tag later you're good to go, and all of the extra stuff (like .vue files) isn't necessary to use the framework.

It's a godsend. I can't imagine how many hours I've lost to obscure webpack errors before switching.

View on HN

You can, of course, do the same with React: https://reactjs.org/docs/add-react-to-a-website.html

But if one would lile to write in jsx, which is the default in react, the doc still guide you to use a preprocessor for production.

Exactly. I can still use jQuery too, but the whole selling point of React is its heavy reliance on JSX.

What webpack errors are you getting with basic create-react-app?

Any production-destined app is going to have to go through some baseline transpiling, linting and minifying, and CRA really shouldn’t be giving you much trouble with the defaults.

Done that. My manager finds it so good when he can hot-fix issue.

Just that some third party plugins are written in es6, it would be cumbersome if you need to support ie11 in a enterprise setting.

Also if you have quite a lot of vue components to load, it would take longer time than compile first with webpack in http1.

>> This is why I stick with Vue. One <script> tag later you're good to go, and all of the extra stuff (like .vue files) isn't necessary to use the framework.

You can do this with React

https://reactjs.org/docs/add-react-to-a-website.html

Reply on news.ycombinator.com