ottomated / create-o7-app Goto Github PK

May you please add a license? Maybe something open source like MIT.

Hey, I've been taking a look at some projects that use inquire and I noticed you are passing down the RenderConfig instance all the way to each prompt call.

I've only glanced at the code so I might have misinterpreted it :) But if that's the case, see if the function to set it globally once might be of interest to you.

If you do not want to re-set the render config object for each new prompt you create, you can call inquire::set_global_render_config to set a global RenderConfig object to be used as the default one for all future prompts.

https://github.com/mikaelmello/inquire#rendering-configuration-aka-color-themes

When using create-o7-app with npm on WSL2:Ubuntu I get the following message:

'\\wsl.localhost\Ubuntu\home\user'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported.  Defaulting to Windows directory.

I could then not use a normal unix-style path to choose my project directory.
I was able to circumvent the issue by using the path: \\wsl.localhost\Ubuntu\home\user\my-o7-app.

When I tried using yarn it worked just fine.
I also tried to see if the issue was with npm so I did create-react-app with npm but that worked as well.
I also tried create-t3-app with npm and it worked as well.

Hey Otto, love what you've done here! The template_builder crate is particularly cool imo, I've been wanting something similar but have always made it too complex or just not been bothered. Different files per combination of features isn't quite as granular as I would ultimately want, but hey if it does the job then I'm down for it.
It'd be great to use in create-rspc-app and probably many more projects, would you be down to get it published? I can lend some time if necessary.

svelte-preprocess@5.0.1 has a dependency on @types/sass which is deprecated, version 5.0.2 fixes this, and the latest version is 5.0.3

I am aware that the version rule ^5.0.1 is supposed to resolve to 5.0.3, but (at least with pnpm) when letting pnpm create o7-app do pnpm install, it still installs 5.0.1

Hi there 👋🏻,
Seems since yesterday there's been an issue using the npm version with dependencies.

Using pnpm in the meantime but I'm quite new to it so it's not ideal and would rather use npm.

Error output when running npm install or similar related npm commands:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/svelte
npm ERR!   svelte@"^4.0.0" from the root project
npm ERR!   peer svelte@"^3.54.0 || ^4.0.0-next.0" from @sveltejs/[email protected]
npm ERR!   node_modules/@sveltejs/kit
npm ERR!     @sveltejs/kit@"^1.20.5" from the root project
npm ERR!     peer @sveltejs/kit@"^1.16.3" from [email protected]
npm ERR!     node_modules/trpc-svelte-query
npm ERR!       trpc-svelte-query@"1.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer svelte@"^3.54.0" from @tanstack/[email protected]
npm ERR! node_modules/@tanstack/svelte-query
npm ERR!   @tanstack/svelte-query@"^4.29.19" from the root project
npm ERR!   peer @tanstack/svelte-query@"^4.29.7" from [email protected]
npm ERR!   node_modules/trpc-svelte-query
npm ERR!     trpc-svelte-query@"1.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

I've got pleb questions, that I don't really want to bother Otto with.

Can you enable the discussions feature, so I can post them there?

Hey Otto,

I've been looking into the project and found out this line, is this intentional?

The planetscale sslaccept will be ?sslaccept=strict

If so can i make a PR to change the above.