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
To my personal taste, there are too many different top-level directories. I suggest to simplify it:
app/.server --> I know that this is a remix/vite feature, but i dont like it. On *nix systems, files, folders starting with a dot means hidden since forever and its until now and are hidden by default. I dont think server logic should be in a hidden folder. Instead i would rather promote the usage of `filename.server.ts` and leave it to the stack user to use this folder or not.
rdt-plugins --> other/rdt-plugins
remix/config.ts --> remix-routes.ts
resources/locales --> app/localization/locales
scripts/cleanup.ts --> move logic to cli
scripts/icon.ts --> already moved to separate package
scripts/{loader.js|setup.ts} --> not sure about them tbh. I dont like that this requires many nested calls and explicitly uses `node` and `npm`. Maybe we can find a less intrusive or opinionated way which allows the stack user to also use other package manager and/or javascript runtimes. Maybe move the logic to its own package and use it as a Shebang instead?
resources/icons --> ?? maybe app/resources/icons?? I would like to have every asset needed for the application contained in `app`
Also for me the terms lib, library, utils, resources are almost interchangeable and too generic to help in organizing files, even more so when they are used at the same time on the same directory level. So i suggest to either make the naming more clear and/or reduce the amount of folders and merge them.
This issue is just a discussion starter!
The text was updated successfully, but these errors were encountered:
I removed rdt-plugins
I would do config/remix-routes.ts instead of a root level file tbh, we can move resources inside of the app I guess. I wonder if that would help Vite properly reload them. icons script I removed but I'm not sure about cleanup though, it shouldn't require you to have our cli for users to cleanup the crap they don't need
loader and setup are required in order to run esm scripts with alias imports and some advanced features. I don't think this can be easily done otherwise, maybe if it was extracted into a separate package it could work but not sure.
library = component library
resources = icons, fonts, translations etc.
utils = generic functions
To my personal taste, there are too many different top-level directories. I suggest to simplify it:
Also for me the terms
lib
,library
,utils
,resources
are almost interchangeable and too generic to help in organizing files, even more so when they are used at the same time on the same directory level. So i suggest to either make the naming more clear and/or reduce the amount of folders and merge them.This issue is just a discussion starter!
The text was updated successfully, but these errors were encountered: