Babel having dependency issues as a compiler?

[drforr]

Actually it's had these issues for ... at least a year to my knowledge.

The official React webpage lists a bunch of possible toolchains, and babel is (significantly, maybe?) at the bottom of the page:

https://reactjs.org/docs/create-a-new-react-app.html

I'm translating the sample ReactJSX => React via CodePen and replacing the 'var XXX = () =>' prefix with 'const XXX =' and so far things seem to work. The Redux toolchain also seems to need, or at least mention babel, so that may be another issue for another day, but I'd be happy just to get the React side working.

Ultimately I'm doing this as learning enough to get Vue+websockets working, because that's what my workplace is standardizing on.

As a side note, in terms of working with the JS toolchains it'd be wonderful to simply name frontend/index.js 'frontend/index.jsx' and have the Perl6 restart mechanisms handle the compilation/bundling for me, but I do realize this is probably better left to the Javascript tools.

Maybe a make-like thing that just quickly checks the timestamps between index.jsx and index.js... but that's another rabbit hole for another time.

[jnthn]

I thought I'd neglected to check in the package lock file, though I wonder if whatever NPM version I used at the time even had one. I certainly don't see one in the directory of the machine where I developed it on. Also, I've no idea if that would have helped...

Anyway, I'll gladly merge a PR that fixes it, but bluntly, I've no patience with the "move fast and break stuff" culture, so I doubt I'll personally be spending any time on it.

[drforr]

Totally understand, I've got much the same problem. sena_kun and I were talking about this, and once I have a PR I'll send it your way