svelteness / kit-docs

Documentation integration for SvelteKit.
https://kitdocs.vercel.app
MIT License
472 stars 33 forks source link

Quickstart broken? #72

Closed baradhili closed 1 year ago

baradhili commented 1 year ago

Following the docs for quick start - it seems to blow up?

npm init @svelteness/kit-docs mydocs

✔ Default KitDocs Theme? (Y/n) · true

[kit-docs]: target directory is empty, creating new SvelteKit app.

create-svelte version 2.3.1

Welcome to SvelteKit!

✔ Which Svelte app template? › Skeleton project
✔ Add type checking with TypeScript? › Yes, using JavaScript with JSDoc comments
✔ Add ESLint for code linting? … No / Yes
✔ Add Prettier for code formatting? … No / Yes
✔ Add Playwright for browser testing? … No / Yes
✔ Add Vitest for unit testing? … No / Yes

Your project is ready!
✔ Type-checked JavaScript
  https://www.typescriptlang.org/tsconfig#checkJs

Install community-maintained integrations:
  https://github.com/svelte-add/svelte-adders

Next steps:
  1: cd mydocs
  2: npm install (or pnpm install, etc)
  3: git init && git add -A && git commit -m "Initial commit" (optional)
  4: npm run dev -- --open

To close the dev server, hit Ctrl-C

Stuck? Visit us at https://svelte.dev/chat
Error: ENOENT: no such file or directory, lstat '/home/bret/Documents/Sites/mydocs/src/routes/index.svelte'
    at Object.lstatSync (node:fs:1574:3)
    at __node_internal_ (node:internal/fs/utils:804:8)
    at rmSync (node:fs:1272:13)
    at main (file:///home/bret/.npm/_npx/cbc22df0399bae1c/node_modules/@svelteness/create-kit-docs/bin/create-kit-docs.js:58:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  errno: -2,
  syscall: 'lstat',
  code: 'ENOENT',
  path: '/home/bret/Documents/Sites/mydocs/src/routes/index.svelte'
}
npm ERR! code 1
npm ERR! path /home/bret/Documents/Sites
npm ERR! command failed
npm ERR! command sh -c -- create-kit-docs mydocs

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/bret/.npm/_logs/2023-01-23T00_12_58_378Z-debug-0.log
mihar-22 commented 1 year ago

It should be now resolved in 1.0, let me know if any issues persists. Thanks!