Interesting example... not sure I'd use it for production as-is... Should really add in some authentication bits (jwt from an auth provider, etc).
Would also be beneficial to wrap a logging service with request/response details and a correlation id with all requests in/out from various service busses. My own tactic is usually newline delimited (\n) JSON to stdout, then you can have a sidecar slurping the logs into an aggregator service for metrics, etc.
Last would be some functional unit testing around some of the core logic bits. Fortunately, with dependency overrides in JS, you don't need to adopt a convoluted DI/IoC system in order to do this.
IMO, hand migration scripts are the single best way to manage schema changes with the database. Some tools will allow separate directories for lists of stored procedures, functions etc. Separate from schema/migration scripts.
With numbered migrations, you are much less likely to experience issues managing an application that is deployed into many environments.
Worth looking into, though not JS specifically is the Dotnet tool "Grate", which is a successor to RoundhousE. The cross db support is very good. If anyone knows of a comparable project for Node/Deno, would be happy to see/hear it. For that matter, it might be interesting to see something in a single executable in Go or Rust. But so far Grate is about the best option I've found.
- https://github.com/erikbra/grate
Avoid recursion in JS, it will end ugly...
function fibonacci(n) {
let nums = [0,1];
for (let i=1; i<n; i++) {
nums = [nums[1], nums[0] + nums[1]];
}
return nums[1];
}
Haven't plated with it, but it looks interesting. Not sure how far it will get used in practice or if/how any node support is... doesn't seem to have any.
Examples are fine... can post the dev.to articles if interresting/prudent as well (see about page on posting rules). TS is okay too. As are github links.
In general the only time I've blocked github or dev.to are specific users/accounts posting a lot of off-topic things... like Python apps in github.
Would suggest limiting non-major version update posts to about once a quarter... there isn't that much news flow here, so too many updates from a project like this will really stick out and start to turn people off.
I understand the desired effect, just pointing out that you may result in the opposite of what you're trying to accomplish.
Also, feel free to post interesting JS/TS finds you come across as well as your own work.
Avoid recursion in JS, it will end ugly... function fibonacci(n) { let nums = [0,1]; for (let i=1; i<n; i++) { nums = [nums[1], nums[0] + nums[1]]; } return nums[1]; }