Cannot run a newly created project #2001

chrisolsen · 2021-07-23T20:59:55Z

Describe the bug

After creating a new project and attempting to start it up with npm run dev, I get the following

ENOENT: no such file or directory, open '/home/chris/Projects/community-sveltekit/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'

Note the duplicate portion of the path .svelte-kit/dev/components

SvelteKit v1.0.0-next.137

Reproduction

https://github.com/chrisolsen/bug-sveltekit

➜ Projects npm init svelte@next community-sveltekit
npx: installed 5 in 1.004s

create-svelte version 2.0.0-next.76

Welcome to SvelteKit!

This is beta software; expect bugs and missing features.

If you encounter a problem, open an issue on https://github.com/sveltejs/kit/issues if none exists already.

✔ Which Svelte app template? › Skeleton project
✔ Use TypeScript? … No / Yes
✔ Add ESLint for code linting? … No / Yes
✔ Add Prettier for code formatting? … No / Yes
✔ Copied project files
✔ Added TypeScript support. To use it inside Svelte components, add lang="ts" to the attributes of a script tag.
✔ Added ESLint.
Readme for ESLint and Svelte: https://github.com/sveltejs/eslint-plugin-svelte3
✔ Added Prettier.
General formatting options: https://prettier.io/docs/en/options.html
Svelte-specific formatting options: https://github.com/sveltejs/prettier-plugin-svelte#options

Want to add other parts to your code base? Visit https://github.com/svelte-add/svelte-adders, a community project of commands to add particular functionality to Svelte projects

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

============
➜ community-sveltekit git:(master) npm run dev

~~TODO~~@0.0.1 dev /home/chris/Projects/community-sveltekit
svelte-kit dev

SvelteKit v1.0.0-next.137

local: http://localhost:3000
network: not exposed

Use --host to expose server to other devices on this network

ENOENT: no such file or directory, open '/home/chris/Projects/community-sveltekit/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'
Error: ENOENT: no such file or directory, open '/home/chris/Projects/community-sveltekit/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'
ENOENT: no such file or directory, open '/home/chris/Projects/community-sveltekit/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'
Error: ENOENT: no such file or directory, open '/home/chris/Projects/community-sveltekit/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'

Logs

No response

System Info

➜  community-sveltekit git:(master) npx envinfo --system --binaries --browsers --npmPackages "{svelte,@sveltejs/*,vite}"
npx: installed 1 in 0.753s

  System:
    OS: Linux 4.19 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 16.92 GB / 25.02 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 12.20.2 - ~/.nvm/versions/node/v12.20.2/bin/node
    npm: 6.14.11 - ~/.nvm/versions/node/v12.20.2/bin/npm
  npmPackages:
    @sveltejs/kit: next => 1.0.0-next.137 
    svelte: ^3.34.0 => 3.40.2

Severity

blocking all usage of SvelteKit

Additional Information

No response

The text was updated successfully, but these errors were encountered:

chrisolsen · 2021-07-23T21:12:19Z

I noticed after pasting my system info that the project was running on node 12.x. After switching to the LTS with nvm and recreating the project everything then worked.

itseMeCode · 2021-07-23T21:54:16Z

Got the same problem also with node 14.17.3.
Demo app is working.

s0kil · 2021-07-23T21:55:34Z

Have the same issue, was just installing node 14.17.3 LTS to test

s0kil · 2021-07-23T21:57:41Z

Here is the error

ENOENT: no such file or directory, open '/home/danielsokil/Lab/s0kil/ECM/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'
Error: ENOENT: no such file or directory, open '/home/danielsokil/Lab/s0kil/ECM/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'
ENOENT: no such file or directory, open '/home/danielsokil/Lab/s0kil/ECM/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'
Error: ENOENT: no such file or directory, open '/home/danielsokil/Lab/s0kil/ECM/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'

s0kil · 2021-07-23T22:15:44Z

Work around is to explicitly use svelte version 3.40.1, "svelte": "3.40.1" in package.json

s0kil · 2021-07-23T22:23:00Z

Turns out that sveltejs/svelte#6089 is the root cause of this issue, checking out that commit triggers the error mentioned above "svelte": "github:sveltejs/svelte#4ca2af41df436ef97cd1953eb67c2c4922a8257b"

Conduitry · 2021-07-24T00:32:56Z

@itseMeCode @s0kil I can't reproduce this with a fresh SvelteKit project, although I haven't tried every permutation of options in the starter script. What are you doing that's leading you to this issue, what package manager are you using, etc?

s0kil · 2021-07-24T01:39:48Z

@Conduitry I'm using pnpm, node 14.17.3, a starter svelte kit project with the static adapter. Created the project with npm init svelte@next my-app

Conduitry · 2021-07-24T01:53:55Z

I can't reproduce this with pnpm dev or pnpm build when using the static adapter, for either the JS- or TS-based demo app.

s0kil · 2021-07-24T01:56:54Z

I've created a new, typescript, eslint, prettier project, added adapter static, updated the packages to latest versions and the error is the same:

Error: ENOENT: no such file or directory, open '/home/danielsokil/Extra/svelte-kit-issue-2001/.svelte-kit/dev/components/.svelte-kit/dev/components/layout.svelte'

Here is the repo: https://github.com/s0kil/svelte-kit-issue-2001

molebox · 2021-07-24T08:38:34Z

Im also getting this error. Clean install (JS, eslint and prettier), skeleton project. Tried switching to node v12 with nvm, still getting error.

basaran · 2021-07-24T08:53:46Z

it seems only the skeleton project is affected. I have been working on creating a lint based carbon skeleton since yesterday, and had made a commit with the last working skeleton:

https://github.com/basaran/sveltekit-carbon

It seems the new one being created is different too. Don't have the layout file.

jessevermeulen · 2021-07-24T09:06:56Z

Same problem here after bumping svelte/kit to 1.0.0-next.137.

basaran · 2021-07-24T09:10:03Z

my yarn.lock from last night is still working with the new skeleton if you copy it prior to yarn install.

https://github.com/basaran/sveltekit-carbon/blob/master/yarn.lock

jessevermeulen · 2021-07-24T09:26:49Z

As @s0kil suggested, downgrading to svelte: 3.40.1 did the trick.

vibhanshu909 · 2021-07-24T13:19:39Z

Hey Guys,
I am facing the same problem, I found a workaround:
So, for some reason, SvelteKit is expecting a script tag with at least one valid expression for __layout/page to work.

Example:

Let's create a new skeleton project.
Install the dependencies.
Since there is no __layout.svelte file, let's create one.
Add the following contents to the __layout.svelte file:

<script>
	0;
</script>
<slot />

Add the following content to index.svelte file:

<script>
	0;
</script>

<p>
	Try editing <strong>src/routes/index.svelte</strong>
</p>

And this seems to fix this issue somehow. Maybe one of SvelteKit's maintainers/contributors can throw some light on it.

I am using node 14.17.0.

simmo · 2021-07-24T13:21:12Z

I'm running NPM @ 7.20.1, Node @ 14.7.3, with Svelte kit @ 1.0.0-next.137.

When running with Svelte @ 3.40.1 there is no issue but updating to 3.40.2 throws the following:

ENOENT: no such file or directory, open '/Users/Mike/Sites/personal/src/lib/icons/src/lib/icons/GitHub.svelte'

The file in question should be '/Users/Mike/Sites/personal/src/lib/icons/GitHub.svelte' so it appears that part of the path is being duplicated.

The file is referenced as import GitHub from '$lib/icons/GitHub.svelte';. Inside a Footer Svelte component. The footer Svelte component is imported by __layout. Refreshing the app seems to loop through several files throwing a duplicated path.

One thing I've noticed is that direct child imports inside of __layout seem to be ok, but anything deeper throws.

As mentioned by others rolling back to 3.40.1 resolves.

simmo · 2021-07-24T13:22:39Z

Also worth saying that this throws in dev but on Vercel I'm not seeing this issue.

firewave-remo · 2021-07-24T14:33:05Z

Same Problem here. Updated an existing Project from SvelteKit v1.0.0-next.131 to 137 und svelte version to 3.40.2.

Can confirm that with svelte 3.40.1 the problem does not exist.

node: v14.17.2

molebox · 2021-07-24T15:06:36Z

So coming back around to this. Ive tried all the above solutions:

use node 12
svelte 3.40.1
added a __layout.svelte component

FWIW ive delete node_modules and lock file too.

None of the above worked.

EDIT: I didnt explicitly do 3.40.1, i had ^3.40.1. Can confirm this works

EDIT 2: I still needed the __layout.svelte file

nstuyvesant · 2021-07-24T20:02:50Z

I am seeing this issue with:
Node 16.5.0
SvelteKit 1.0.0-next-137
Svelte 3.40.2

Worked around it with

<script>
let workaround = true
</script>

kampsy · 2021-07-25T08:07:01Z

Same problem when i create a new skeleton project

Node v14.17.3
SvelteKit v1.0.0-next.137
Svelte v3.34.0

What works for me

npm init svelte@next my-app
cd my-app
replace "svelte": "^3.34.0" with "svelte": "3.40.1" in package.json
create __layout.svelte file in src/routes and add <slot></slot>
npm install
npm run dev -- --open

antony · 2021-07-25T09:37:54Z

@kampsy you don't need to create the __layout.svelte file. Just upgrading Svelte fixes it.

molebox · 2021-07-25T09:44:58Z

@kampsy you don't need to create the __layout.svelte file. Just upgrading Svelte fixes it.

This wasnt true for me. I had to create the __layout.svelte file too. Also, its a downgrade 3.34.0 > 3.40.1. But, tomato, tomato and all that jazz

kampsy · 2021-07-25T10:12:31Z

@antony like @molebox points out. It doesn't work without layout for me.

joeczar · 2021-07-25T11:11:27Z

Hi, I've had no success with the same setup as @kampsy. I added the __layout.svelte and upgraded to 3.40.1. The Error has changed to not being able to find the __layout.svelte.

https://github.com/joeczar/sveltekit-portfolia

kampsy · 2021-07-25T11:33:29Z

@joeczar remove "^" from "svelte": "^3.40.1" then run npm install

its working for me

joeczar · 2021-07-25T11:50:43Z

Thanks @kampsy! It's running now.

joelhickok · 2021-07-25T22:39:29Z

Still having this problem despite comments immediately above. Didn't take the time to read all the comments above, but all I can say is just ensure that each .svelte template includes a script tag with at least one valid line of JavaScript. I'm using svelte 3.40.2 and @sveltejs/kit 1.0.0-next.137.

Such as:

<script>
    console.log('test')
</script>

donpark · 2021-07-26T06:11:50Z

Downgrading to "svelte": "3.40.1" fixed it for me. "@sveltejs/kit" version is "1.0.0-next.137".

In my case, it was import FooBar from "$lib/FooBar.svelte" throwing ENOENT error showing file path with .../src/lib/src/lib/FooBar.svelte when running with svelte-kit dev but not with svelte-kit preview.

dominikg · 2021-07-26T08:32:10Z

Just found this PR on vite: vitejs/vite#2904 that looks like it fixes this (and may log a warning for the invalid sourcemap source)

Conduitry · 2021-07-26T16:42:24Z

From my local tests with the latest HEAD of Vite, it looks like this issue is already resolved, and so hopefully that PR will be included in tomorrow's Vite release.

I am also getting the warnings about Sourcemap for "/foo/.svelte-kit/dev/components/layout.svelte" points to missing source files.

@dominikg I'm still not entirely sure what sveltejs/svelte#6089 was initially intended to do. Does this warning we'd now be getting from Vite indicate that there is in fact something wrong with our sourcemaps, but it's just that Vite will be able to cope better with that?

dominikg · 2021-07-26T17:46:12Z

@dummdidumm would know better but it seems like that PR adds a missing source entry to the first map when combining sourcemaps to avoid a potential upstream issue in remapping.

The added source entry caused vite to attempt to read the source but the constructed path to that is wrong (see duplicate .svelte-kit/dev/components/ in description) and errors. The next vite version scheduled to be released tomorrow (27.) prints a warning instead, unblocking the use of svelte 3.40.2.

We still need to figure out why that path is wrong, but the warnings from vite might help with that.

TL;DR For those affected by this issue:
With vite <= 2.4.3 , use svelte <= 3.40.1
Once vite 2.4.4 (or 2.5.0) has been released, you can update vite and svelte to try again.

jacktho · 2021-07-26T22:01:36Z

This is still happening with 3.40.3 (as expected per dominikg's comment I guess).

dominikg · 2021-07-27T12:32:47Z

vite 2.4.4 has been released and the skeleton project works again.

Instead of an error, vite just prints a warning now.

dominikg@mb14:~/develop/reproductions/kit-vite-244$ pnpm ls vite --depth=Infinity
Legend: production dependency, optional only, dev only

~[email protected] /home/dominikg/develop/reproductions/kit-vite-244

devDependencies:
@sveltejs/kit 1.0.0-next.137
├─┬ @sveltejs/vite-plugin-svelte 1.0.0-next.14
│ └── vite 2.4.4 peer
└── vite 2.4.4
dominikg@mb14:~/develop/reproductions/kit-vite-244$ pnpm dev

> ~[email protected] dev /home/dominikg/develop/reproductions/kit-vite-244
> svelte-kit dev


  SvelteKit v1.0.0-next.137

  local:   http://localhost:3000
  network: not exposed

  Use --host to expose server to other devices on this network


Sourcemap for "/home/dominikg/develop/reproductions/kit-vite-244/.svelte-kit/dev/components/layout.svelte" points to missing source files
Sourcemap for "/home/dominikg/develop/reproductions/kit-vite-244/src/routes/index.svelte" points to missing source files

alexbruno · 2021-07-27T14:16:22Z

I think the point is /src/routes/path/index.svelte files.
I have a project made from a Skeleton that was working with no errors or warnings.
But when I create a /src/routes/blog/index.svelte it raises the error.
Update Vite version fix it with this warning above.

eden-lane · 2021-07-27T17:30:46Z

I'm not sure why is it closed. What is the solution?

alexbruno · 2021-07-27T18:12:43Z

@eden-lane try to uninstall and reinstall @sveltejs/kit.
By doing it you will get it with the latest Vite version. It fixes the error, but shows warnings for now.

chrisolsen closed this as completed Jul 23, 2021

basaran mentioned this issue Jul 24, 2021

sveltekit skeleton project file not found #2004

Closed

chrisolsen reopened this Jul 24, 2021

Conduitry mentioned this issue Jul 24, 2021

svelte-kit dev doesn't work due to "no such file" error #2005

Closed

This was referenced Jul 24, 2021

Svelte component with global styles only cannot be found in dev vitejs/vite#4383

Closed

Regression introduced in PR #5870 sveltejs/svelte#6567

Closed

nstuyvesant mentioned this issue Jul 24, 2021

Dependency error with SvelteKit v1.0.0-next.137 bestguy/sveltestrap#344

Closed

antony added the bug Something isn't working label Jul 25, 2021

benmccann mentioned this issue Jul 25, 2021

Revert "[fix] add filename to combined source map if needed (#6089)" sveltejs/svelte#6572

Closed

Conduitry mentioned this issue Jul 26, 2021

Wrong path resolution to components into $lib at dev server start #2015

Closed

Conduitry added the vite label Jul 26, 2021

bluwy mentioned this issue Jul 27, 2021

Creating skeleton svelte app with everything else set to true sveltejs/svelte#6579

Closed

Conduitry closed this as completed Jul 27, 2021

dominikg mentioned this issue Jul 28, 2021

Sourcemap for "/.../...svelte" points to missing source files (if empty script tag) #2029

Closed

Cannot run a newly created project #2001

Cannot run a newly created project #2001

Comments

chrisolsen commented Jul 23, 2021

Describe the bug

Reproduction

Logs

System Info

Severity

Additional Information

chrisolsen commented Jul 23, 2021

itseMeCode commented Jul 23, 2021 • edited Loading

s0kil commented Jul 23, 2021

s0kil commented Jul 23, 2021

s0kil commented Jul 23, 2021

s0kil commented Jul 23, 2021

Conduitry commented Jul 24, 2021

s0kil commented Jul 24, 2021

Conduitry commented Jul 24, 2021

s0kil commented Jul 24, 2021

molebox commented Jul 24, 2021

basaran commented Jul 24, 2021

jessevermeulen commented Jul 24, 2021 • edited Loading

basaran commented Jul 24, 2021 • edited Loading

jessevermeulen commented Jul 24, 2021

vibhanshu909 commented Jul 24, 2021

Example:

simmo commented Jul 24, 2021 • edited Loading

simmo commented Jul 24, 2021

firewave-remo commented Jul 24, 2021

molebox commented Jul 24, 2021 • edited Loading

nstuyvesant commented Jul 24, 2021 • edited Loading

kampsy commented Jul 25, 2021 • edited Loading

What works for me

antony commented Jul 25, 2021

molebox commented Jul 25, 2021 • edited Loading

kampsy commented Jul 25, 2021

joeczar commented Jul 25, 2021 • edited Loading

kampsy commented Jul 25, 2021

joeczar commented Jul 25, 2021

joelhickok commented Jul 25, 2021

donpark commented Jul 26, 2021 • edited Loading

dominikg commented Jul 26, 2021

Conduitry commented Jul 26, 2021

dominikg commented Jul 26, 2021

jacktho commented Jul 26, 2021

dominikg commented Jul 27, 2021

alexbruno commented Jul 27, 2021

eden-lane commented Jul 27, 2021

alexbruno commented Jul 27, 2021

itseMeCode commented Jul 23, 2021 •

edited

Loading

jessevermeulen commented Jul 24, 2021 •

edited

Loading

basaran commented Jul 24, 2021 •

edited

Loading

simmo commented Jul 24, 2021 •

edited

Loading

molebox commented Jul 24, 2021 •

edited

Loading

nstuyvesant commented Jul 24, 2021 •

edited

Loading

kampsy commented Jul 25, 2021 •

edited

Loading

molebox commented Jul 25, 2021 •

edited

Loading

joeczar commented Jul 25, 2021 •

edited

Loading

donpark commented Jul 26, 2021 •

edited

Loading