$lib/components" does not use an existing path alias defined in your jsconfig.json

[ianengelbrecht]

Describe the bug

I'm using a Svelte (not SvelteKit) project managed with Vite, no typescript. When I run npx shadcn-svelte@latest init I get a message $lib/components" does not use an existing path alias defined in your jsconfig.json.

jsconfig looks has this:

"paths": {
    "$components": ["src/components"],
    "$components/*": ["src/components/*"],  
    "$utils": ["src/utils"],
    "$utils/*": ["src/utils/*"] 
  }

vite.config has:

resolve: {
    alias: {
      $lib: path.resolve("./src/lib"),
      $components: path.resolve("./src/components")
    },
  }

Thanks!

The vite installation of Svelte only comes with $lib, I added $ components and $utils myself, perhaps init should update the config files for you?

Reproduction

https://github.com/ianengelbrecht/svelte-shadcn-time-picker

Clone, install, and try npx shadcn-svelte@latest init

Logs

No response

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 13th Gen Intel(R) Core(TM) i5-1345U
    Memory: 17.81 GB / 31.66 GB
  Binaries:
    Node: 20.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (129.0.2792.89)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    svelte: ^5.1.3 => 5.1.13

Severity

blocking all usage of shadcn-svelte

[ianengelbrecht]

Confirmed that this does not occur with a project created with npm create vite@latest my-app -- --template svelte-ts

[ieedan]

I opened a PR on your repo that fixes the config files. I don't believe we make any changes to jsconfig.json so maybe some documentation would help here?

[ieedan]

Can you create a new repro without trying to update the config files yourself? In this case the config files were just incorrectly modified.

[ianengelbrecht]

Same error on a new repo with no changes to jsconfig or vite.config files. Also, I don't see any actual changes in jsconfig in the PR other than changed indentation so perhaps something didn't get committed there. Thanks for looking into this!

…

On Sun, Nov 10, 2024 at 4:10 PM Aidan Bleser ***@***.***> wrote: Can you create a new repro without trying to update the config files yourself? In this case the config files were just incorrectly modified. — Reply to this email directly, view it on GitHub <#1474 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACH3QI6ITHR2TDU7YDXFWKDZ75SLVAVCNFSM6AAAAABRQEBKEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWG42TCMRZGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Ian Engelbrecht Digitization Coordinator Natural Science Collections Facility South Africa *https://nscf.org.za/ <https://nscf.org.za/>* +27 82 763 4596 i ***@***.***>***@***.*** / ***@***.***

[ieedan]

Take another look its its adding an import and moving the options.

Please share the repro.

[Nokorbis]

I have the same issue with a project created with
Tauri (2.1.1)+ Svelte-kit ( (2.8.1) [svelte 5.2.0]

It was however fixed by running vite (or at least pnpm tauri dev, which I guess runs vite) AFTER adding an alias in svelte.config.js and BEFORE running the command pnpm dlx shadcn-svelte@next init

[huntabyte]

Oh yeah that initial step is responsible for building out the appropriate tsconfig.json / jsconfig.json @Nokorbis

[huntabyte]

If someone wants to add "run your dev server once" to the docs we can probably close this issue

[AdrianGonz97]

fixed by #1487