Radu
@radu-b.bsky.social
Blabbing a lot about fixing problems with JS.
Living the life at RebelDot.
Living the life at RebelDot.
Writing unit tests will never be the same after your talk! My intuition told me we should only test business logic, but was having a hard time identifying it. You managed through your talk to shed light on the topic for me! 🙇
May 30, 2025 at 8:15 AM
Writing unit tests will never be the same after your talk! My intuition told me we should only test business logic, but was having a hard time identifying it. You managed through your talk to shed light on the topic for me! 🙇
That was my TED Talk, thank you for your attention 🤭
March 26, 2025 at 9:54 PM
That was my TED Talk, thank you for your attention 🤭
In the meanwhile, test Tanstack Start while in Beta and share your opinion to the world. If you have any feedback, share it with the dev team and the community. Report bugs and engage in conversations around known issues.
March 26, 2025 at 9:54 PM
In the meanwhile, test Tanstack Start while in Beta and share your opinion to the world. If you have any feedback, share it with the dev team and the community. Report bugs and engage in conversations around known issues.
We need alternatives and my gut feeling is that @tanstack.com Start has the potential to deliver the meta-framework React deserves. Can’t wait for it to be ready for production.
March 26, 2025 at 9:54 PM
We need alternatives and my gut feeling is that @tanstack.com Start has the potential to deliver the meta-framework React deserves. Can’t wait for it to be ready for production.
Ideally I'd want to keep the route path, but change its configuration entirely based on the migration feature flag.
Let's say we have V1 of route A and V2 of the same Route A. Is there a way to conditionally rebuild the route at runtime so users could see V2 only when the feature is finished?
Let's say we have V1 of route A and V2 of the same Route A. Is there a way to conditionally rebuild the route at runtime so users could see V2 only when the feature is finished?
March 11, 2025 at 3:40 PM
Ideally I'd want to keep the route path, but change its configuration entirely based on the migration feature flag.
Let's say we have V1 of route A and V2 of the same Route A. Is there a way to conditionally rebuild the route at runtime so users could see V2 only when the feature is finished?
Let's say we have V1 of route A and V2 of the same Route A. Is there a way to conditionally rebuild the route at runtime so users could see V2 only when the feature is finished?
Adding that to my extensions list! Thanks mate! Will come back with feedback.
February 19, 2025 at 4:47 PM
Adding that to my extensions list! Thanks mate! Will come back with feedback.
Never tried that... But it would be a nice thing to have.
I remembered though that I also make use of Sonarqube for IDE - but this is not auditing npm packages, it just helps with writing clean code.
docs.sonarsource.com/sonarqube-fo...
I remembered though that I also make use of Sonarqube for IDE - but this is not auditing npm packages, it just helps with writing clean code.
docs.sonarsource.com/sonarqube-fo...
SonarQube for VS Code Documentation
The SonarQube for VS Code documentation explains everything you need to know about using this advanced linter to write Clean Code in your IDE.
docs.sonarsource.com
February 18, 2025 at 9:02 PM
Never tried that... But it would be a nice thing to have.
I remembered though that I also make use of Sonarqube for IDE - but this is not auditing npm packages, it just helps with writing clean code.
docs.sonarsource.com/sonarqube-fo...
I remembered though that I also make use of Sonarqube for IDE - but this is not auditing npm packages, it just helps with writing clean code.
docs.sonarsource.com/sonarqube-fo...
We ran it in the CI as a first step. If there were any major risks the CI would break.
There were times when it proved itself inconvenient, but it did create quite the fuss for the stakeholders. The devs were happy, because it justified investigating the issue.
There were times when it proved itself inconvenient, but it did create quite the fuss for the stakeholders. The devs were happy, because it justified investigating the issue.
February 18, 2025 at 6:10 PM
We ran it in the CI as a first step. If there were any major risks the CI would break.
There were times when it proved itself inconvenient, but it did create quite the fuss for the stakeholders. The devs were happy, because it justified investigating the issue.
There were times when it proved itself inconvenient, but it did create quite the fuss for the stakeholders. The devs were happy, because it justified investigating the issue.
I have successfully used Trivy in the past and it made wonder with auditing both npm dependecies and environment ones. I suggest checking it out.
aquasecurity.github.io/trivy/v0.18.3/
aquasecurity.github.io/trivy/v0.18.3/
Trivy
A Simple and Comprehensive Vulnerability Scanner for Containers and other Artifacts, Suitable for CI
aquasecurity.github.io
February 18, 2025 at 1:16 PM
I have successfully used Trivy in the past and it made wonder with auditing both npm dependecies and environment ones. I suggest checking it out.
aquasecurity.github.io/trivy/v0.18.3/
aquasecurity.github.io/trivy/v0.18.3/
Your piece reminded me that I’ve read something similar in the past. Leaving here a link for whoever stumbles on this comment to explore.
And thank you, Travis for the reminder! 🙇
fs.blog/map-and-terr...
And thank you, Travis for the reminder! 🙇
fs.blog/map-and-terr...
The Map Is Not the Territory
The map is not the territory reminds us that our mental models of the world are not the same as the world itself. It cautions against confusing our abstractions and representations with the complex, e...
fs.blog
February 12, 2025 at 12:33 PM
Your piece reminded me that I’ve read something similar in the past. Leaving here a link for whoever stumbles on this comment to explore.
And thank you, Travis for the reminder! 🙇
fs.blog/map-and-terr...
And thank you, Travis for the reminder! 🙇
fs.blog/map-and-terr...
Woah, that is some great content! 🥹
February 5, 2025 at 9:27 AM
Woah, that is some great content! 🥹
I don’t know which is the vulnerability. However, I would bet that you could mitigate it by applying a bit of input validation. Zod can be a great contestant for that.
February 3, 2025 at 10:06 AM
I don’t know which is the vulnerability. However, I would bet that you could mitigate it by applying a bit of input validation. Zod can be a great contestant for that.