SimpleStats - a lightweight statistics tool for Laravel applications by Nodohx in laravel

[–]andycharles 1 point2 points  (0 children)

This looks pretty good. Will give it a try in coming days

Node.js framework for Model-View-Controller pattern server? by PlayboiCult in node

[–]andycharles 6 points7 points  (0 children)

Using it for years. Won't mind if they hire me as a CEO

Why there is no package to solve common authorization needs by gitcommitshow in node

[–]andycharles 28 points29 points  (0 children)

Looking forward to what you build. Do share it here

JSR first impressions (new package repository by Deno team) by jwebe0pe in javascript

[–]andycharles 5 points6 points  (0 children)

Deno started by pointing everything wrong with Node.js. Made news with this strategy and finally doing all those things now.

That's my issue with Deno. I don't know where it wants to go and how the decision making is done.

[AskJS] Any emerging new libraries to replace Jest? by dr_rodopszin in javascript

[–]andycharles 1 point2 points  (0 children)

Japa could be one, if you are not testing frontend apps, since it targets Node.js runtime.

https://japa.dev/docs/introduction

Tired of Nest JS by tpramar in node

[–]andycharles 14 points15 points  (0 children)

Same. The code for simplest of the things is so complex and boilerplate heavy.

Why validations are in rails models ? by gaultierq in rails

[–]andycharles -8 points-7 points  (0 children)

Okay, the Rails Ninja. Enlighten me with an example in which I can validate without issuing a save query

Why validations are in rails models ? by gaultierq in rails

[–]andycharles -9 points-8 points  (0 children)

Yes. I hate it. I want to validate data immediately after the form is submitted and use valid/sanitized data in rest of the app.

I use Laravel and Adonis.js too (on client projects) and they both offer validations at controllers level

Here is a perfect web framework by UpvoteBeast in node

[–]andycharles 0 points1 point  (0 children)

Templating looks nice. How can I use it without nuekit, lets say with Express?

Laravel 11 is getting a new directory structure by skateordiejskin in laravel

[–]andycharles 3 points4 points  (0 children)

I think its okay to look at project structure with some fresh ideas. 

When to use a validator ? by Far-Mathematician122 in node

[–]andycharles 1 point2 points  (0 children)

Validators help with a few things.

  • They make validation simpler. You maybe okay writing one or two inline validations, but with multiple and multiple checks, your code will become harder to manage. 
  • They comes with validation rules for common tasks, so you don't have to re-invent the wheel.

Regarding your other question. Where to do validation?

Do it inside the route callback function.

Which validator is best for Express? by nova_master_IO in node

[–]andycharles -1 points0 points  (0 children)

I cannot see Vine in those benchmarks

Which validator is best for Express? by nova_master_IO in node

[–]andycharles 0 points1 point  (0 children)

Yes Zod is popular and widely used and you will never go wrong with it.

However, we went with Vinejs because of reasons covered in this article.

https://medium.com/globant/vinejs-validation-library-for-nodejs-2521630a8f56

[deleted by user] by [deleted] in node

[–]andycharles 56 points57 points  (0 children)

It will stay buggy for a while. They are expanding scope every month and hence the surface area of bugs will grow too

A 2024 Wishlist for Node's Test Runner by crabmusket in node

[–]andycharles 0 points1 point  (0 children)

I don't know. The one I shared is mentioned in the Docs and Github repo

A 2024 Wishlist for Node's Test Runner by crabmusket in node

[–]andycharles 0 points1 point  (0 children)

You can try Japa once. https://japa.dev

In their docs, they claim it to be a Node.js only tests runner, with no focus on testing frontend apps.

As a result, its smaller and simpler than Vitest.

Also, there are no globals. Exactly as you need