#about node builtins, alternatives and best practice.
2 messages · Page 1 of 1 (latest)
no, it is not a bad practice, it just has to be a concious decision because it's hard to change if you want to migrate to another adapter or share your code with others using other adapters. To make migration easy, it is always a good idea to check the Astro runtime API first https://docs.astro.build/en/reference/api-reference/ but if you want to take advantage of SSR, you need to go beyond that. You can think how your code would look like in netlify, vercel, deno deploy. Deno also has a custom API not matching node. But if all of this is out of scope and your project is set with node till its end of life, then who cares. in this Theme, I used node fs intensively, even express, passport, you can just have a look https://astro.build/themes/details/astro-big-doc/