You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the configuration files all use different filetypes:
ts
js
mjs
cjs
json
yml
I believe for the sake of consistency, we should try to keep the amount of different filetypes to a minimal.
I've made a table below about what software supports what filetypes:
Software
json
ts
ESModule
CommonJS
Tailwind
❌
✔️
✔️
✔️
Prettier
✔️
❌
✔️
✔️
PostCSS
❌
❌
❌
✔️
Next
❌
❌
✔️
✔️
Drizzle
✔️
✔️
✔️
❌
ESLint
✔️
❌
✔️
✔️
The text was updated successfully, but these errors were encountered:
So my opinion on configuration files is the following:
It doesn't matter if they are all the same filetype or not, what matters the most is the type-safety, it's one of the core values of this project and so with that here is the order in which configuration files should be in by their compatibility:
TypeScript
ESModule
CJS
JSON
Typescript just comes with the type-safety built-in and it's my preferred choice for config files, ESM and CJS both are the next best thing because you can still use jsdoc comments and checkJS in the tsconfig to get type-checking in them, and if all fails then json it is.
Currently, the configuration files all use different filetypes:
I believe for the sake of consistency, we should try to keep the amount of different filetypes to a minimal.
I've made a table below about what software supports what filetypes:
json
ts
The text was updated successfully, but these errors were encountered: