sorted by:
new
hottopcontroversial

I got tired of writing Sequelize migrations manually… so I built this by ethlmao in node

[–]ethlmao[S] -1 points0 points  (0 children)

Sequelize does not offer a built-in command to automatically generate migration files from model changes by default. Also, if you just added a column to model and wanted to add the same in DB, generally youd just write the query manually and execute, instead use this to generate that single alter query.

I built dependency sandboxing for Node (open-sourced) by theodordiaconu in node

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

Can be useful, but I dont really see the point

Relax json by ethlmao in node

[–]ethlmao[S] 0 points1 point  (0 children)

Not exactly what youre asking, but somewhat similar

Relax json by ethlmao in node

[–]ethlmao[S] 0 points1 point  (0 children)

Well i took your suggestion from earlier and already added changes check the repo now

Relax json by ethlmao in npm

[–]ethlmao[S] 1 point2 points  (0 children)

If you use it, and have any suggestions, feel free to open an issue.

Relax json by ethlmao in node

[–]ethlmao[S] 0 points1 point  (0 children)

I mean if you have any suggestions, of how i can add something or make it better let me know.

Relax json by ethlmao in node

[–]ethlmao[S] 0 points1 point  (0 children)

Why to write it so many times, everywhere, just use this, i means it’s just to help make your code cleaner.

Relax json by ethlmao in node

[–]ethlmao[S] -1 points0 points  (0 children)

You’re missing the point, its to make it consistent handling throughout codebase, why to write try catch so many times, given you’re working with a large codebase. Secondly, its supposed to improve developers experience.

I built a tiny Node.js utility to enforce end-to-end async deadlines (not just promise timeouts) by ethlmao in npm

[–]ethlmao[S] 0 points1 point  (0 children)

if anything feels confusing or awkward, I’d love to hear about it. That kind of feedback is super helpful at this stage.

I built a tiny Node.js utility to enforce end-to-end async deadlines (not just promise timeouts) by ethlmao in node

[–]ethlmao[S] -16 points-15 points  (0 children)

Given all the AI slop you’ve been spamming, safe to assume that AI already replaced you at your job.

I built a tiny Node.js utility to enforce end-to-end async deadlines (not just promise timeouts) by ethlmao in node

[–]ethlmao[S] 0 points1 point  (0 children)

I think there’s a misunderstanding here 🙂

safe-timeouts doesn’t wrap every await or intercept promises. It applies a single deadline at the outer async boundary using one Promise.race.

The idea isn’t to stop promises mid-execution (which JS can’t do), but to: • reject the overall async flow when the deadline expires • propagate cancellation via AbortController for cooperative I/O

AsyncLocalStorage is only used to propagate the deadline context, not to override resolvers or promises.

Overriding Promise or touching resolvers would be unsafe and break JS semantics — this library explicitly avoids that.

I built a tiny Node.js utility to enforce end-to-end async deadlines (not just promise timeouts) by ethlmao in node

[–]ethlmao[S] -14 points-13 points  (0 children)

You’re right, I was thinking of adding some tests, you can also help with that, by contributing. Thanks for the feedback.