There are good reasons why the outdir might need to be moved.
Usually it's to better fit pre-defined import aliases from the framework. For example placing it in src/lib/paraglide when using SvelteKit so that we can import with $lib/paraglide. NextJS is also starting to push a folder-structure where there is no src/ folder.
Thus, people often need to change the outdir, which can be annoying to do.
Proposal
Explicitly prompt for the outdir when running paraglide-js init with src/paraglide as the default value.
IMO explicitly prompting users for configuration with sensible defaults is preferable over assuming defaults, because then they are at least aware that something can be configured.
Context/Problem
There are good reasons why the
outdirmight need to be moved.Usually it's to better fit pre-defined import aliases from the framework. For example placing it in
src/lib/paraglidewhen using SvelteKit so that we can import with$lib/paraglide. NextJS is also starting to push a folder-structure where there is nosrc/folder.Thus, people often need to change the
outdir, which can be annoying to do.Proposal
Explicitly prompt for the
outdirwhen runningparaglide-js initwithsrc/paraglideas the default value.IMO explicitly prompting users for configuration with sensible defaults is preferable over assuming defaults, because then they are at least aware that something can be configured.