Hacker News new | past | comments | ask | show | jobs | submit | rk06's comments login

If the features were actually cut, then that would be a separate discussion point. However, that was not the case, the author directly says that the features are still there but restricted to blessed set of users. So, author considers elm to be crippleware

In theory, yes Vite is webpack replacement. CRA is a different beast. So, what is CRA’s replacement? Vite + vite-plugin-react.

But that is quite a mouthful, so people shorten it to Vite. So, when they say switch to Vite, Vite-react plug-in is implied. No one is recommending rolling your own Vite plug-in for react


CRA does much more than just supporting jsx, which any bundler should be able to do without a "plugin".

What else does that plugin do? HMR? Equivalence to CRA is next, which is a set of opinionated loaders and config. But next also has the router and some react utils on top.


So, like using vue/alpine with a script tag?

if you want to go no-build (i.e. SPA without nodejs and npm), then your options are limtied to Vue and Alpine


Is there a way one can make a JS fetch() call and instruct browser to not send cookies etc, so CORS limitation won't be applied?

CORS is basically happening because of the sensitive data that browser sends by default, so if browser is not sending such info, then CORS also need not be applied


The default is quite the opposite. Whether fetch sends credentials is controlled by the 'credentials' option, which defaults to "same-origin".

https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/U...


> CORS is basically happening because of the sensitive data that browser sends by default, so if browser is not sending such info, then CORS also need not be applied

Can you cite where this behaviour is defined?


I am just asking if there is a way around it. I know CORS is in palce due to browser sending cookie and auth info by default with HTTP requests. other poster mentioned that fetch does have this behavior, but I have not seen if such requests will be blocked by CORS or not

Ah okay. It didn't appear to be a question at all. In that case, I'd say yes that might well make sense. CORS is a bit of a cudgel.

It has been the case for years. Dan abramov admitted that CRA is on maintenance mode in 2021, but as the issue states, "CRA deprecation is not noted anywhere".

After the recent blow up which resulted in the linked GitHub issue, react core team has officially added note that "CRA is deprecated" and marked CRA as deprecated in npm.

One would argue that it is already the case since, but it is also the case that Vite is current goto for React SPA, but react team still disagree on it.


UseEffect(), dependency tracking, too much re-renders??

Problems galore in react, you should try out new js frameworks. Atleast vue and solid, to see what else is on the table


There are definitely problems with react, but I think his point was that they're not big enough to justify a change.

Though I agree trying other frameworks is a good practice. See what you're missing, or understand your preferred framework better.


What is there to hear? They asked ridiculous questions. Interviewee showed above average competence. So, they should have moved to next interview for cultural fit.


it is great to say support for vanilla js & vue in addition to react, for other js framework to consume


They are really good. And but my android phone (on android 13) doesn't support it. So what should I do? Buy another phone?


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: