News for hackers. Stuff that matters.
Re:Writing secure Go code by rollulus on Monday November 04, 2024 @02:50PM (#42045387)
My few tiny steps in JS world were alienating in that sense: having a brand new install of all tools, doing a “npx create-react-app” and got greeted with “congrats, your app is initialised, it has 13 vulnerable dependencies”.
Re:Writing secure Go code by vdvsvwvwvwvwv on Monday November 04, 2024 @04:19PM (#42046068)
Worse CRA goes from saviour to deprecated, "use nextjs or vite instead" in a blink. Meta should maintain it. Nextjs will probably morph again in the future so you hope investing in learning vite is the answer. JS has this way.

Meanwhile Rails is so old it is thinking it needs to find a partner, settle down and buy a picket fenced house.

Re:Writing secure Go code by mplewis on Monday November 04, 2024 @09:25PM (#42048077)
Unfortunately, in Rails, your major breaking changes without a migration path come from the core team.
Re:Writing secure Go code by hombre_fatal on Monday November 04, 2024 @03:14PM (#42045588)
Tbf those are development deps rather than production server deps, and the vuln will be something like "DOS possible if you let users craft their own regex string as input to lib.foo(re) in a server ctx" rather than "by using this in development to build your static js app, people get remote access to your dev machine."
Re:Writing secure Go code by robertlagrant on Monday November 04, 2024 @04:06PM (#42045977)
It is a bit silly then that it reports them as vulnerabilities by default.
Re:Writing secure Go code by veidelis on Tuesday November 05, 2024 @07:58AM (#42051140)
create-react-app is not maintained AFAIK