Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "react.js"
-
I’m so sorry if this is the place for questions. I’m terrified of stack overflow and have been searching for a week for a solution and can’t find one. This is for React.js people.
I was tasked to create a webpage with react. The limitation is, they did not wanna adopt the node.js dependency. I said ok, I’ll figure it out. You can inject react, material UI, and babel with script tags in HTML, then put ur lil components in it. I did that and it works beautifully.
However, now I have to write tests for this. I think it’s actually impossible without a way to render React, so I have to use the browser, or node, right? I convinced my boss to allow me to use a node.js container just for testing, which I thought would make my life easier.
I don’t know how to render this thing with node. It’s just an HTML file that pulls react via script tags, and idk how to serve html with node. Additionally, none of the React testing libraries seem to support testing a system that wasn’t designed to be served with node, at least not easily. My gut tells me that the complication with how things are imported contributes at least a little to this (dependencies pulled via script tags in the HTML file and made available to react through global const variables).
I could be wrong about any of this — im fairly new. But how tf do I go about testing these react components? For reference, if you go to Reacts docs, there’s a section called “add react to a page in one minute” that’s pretty much what I did.20 -
The most annoying question, that has been asked many times through centuries.. here it goes again:
What Editor would you choose for Web, React.js, React Native and Flutter on Mac:
Atom || VSCode8 -
JavaScript development turns into more and more of a shitshow over time. Not that it was great at the beginning, but with each passing year it gets worse.
There are now 17 versions of Node.js, 18 versions of React.js, 3 major versions of Vue.js... Each version brings something new and no one is in a rush to update their stuff to be compatible with the latest version of the framework3 -
My current assignment is to refactor a React app and get it up to speed. All dependencies have been updated and necessary changes made. Currently I’m working to get class components moved to functional components when React hooks can replace the lifecycle methods used. Additionally I am updating it with ESLint to follow the Google JavaScript Style Guide because the code quality is questionable. What are some of the things you’d do to refactor a React application?5
-
Can a React.JS expert help me to understand something?
In short, I would like to know what are the main differences between react version 15.6 and 17, in terms of browser issues, and component compatibility?
We have a legacy code base that is in version 15.6 and the team wants to upgrade it and I am attempting to argue with my dumb CTO to upgrade to version 17. However, I’m not versed in react, I'm just a PO and the CTO doesn't know anything but for some odd reason is adamant about staying on an older version. The developers gave me their opinion but I'm interested in an outside opinion.5