-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deno 2 compile doesn't work on sveltekit (error: Module not found runtime/control.js) #26155
Comments
@SerJaimeLannister may i ask if that's really all the content of your file |
Okay. I was able to reproduce. Mine is also looking for |
Were you able to fix this @uncomfyhalomacro |
Nope. but i found out how to "make it run". Here is what I did
It's kind of broken but it's also beyond my abilities. |
Hmm , this is kind of "good enough support" and though I appreciate your efforts , I don't think this is worth enough to close this issue Hopefully someone from the deno team can fix this completely |
I found the main issue and opened a new ticket (#26233) to make it easier to reproduce. So, we can close this and proceed with the new (#26233). You can do some workarounds for this issue. Go into index.js and remove each JSDoc comments with That will make the compile successful. |
Hey so I did try to remove the as a workaround and it still doesn't work , do I need to remove this jsdoc comment + import on each file of my project? |
|
Oh, I found a solution. It's not a bug. Use
|
hey just a minor nitpick , we don't need to have this for build/server/index.js but rather build/index.js also when I reload , it actually shows asset to be a 404 for some time but just going to a different page makes it work , its very bizarre to say the least and actually gives this error
sveltekit-test.mp4 |
Also I think deno should give a warning / custom flag that hey you should do --no-check like how it does for --unstable-sloppy-imports and even then as in the recent issue by @marvinhagemeister (I know this is amature but I tried looking for the issue but I couldn't find the issue created by marvin for --unstable-sloppy-imports) but If I remember correctly it was about asking at the runtime to enable unstable-sloppy-imports. I think something like this should also be done with deno compile --no-check also , fixing the issue as of the video could be of some priority |
I thought your issue in compile (step 9) gives you this error.
and that is mentioned on the label of bug So, to get build without error module not found (that's error occurs in import in commented JSdoc, it's not bug), use |
I thought an outside bug was the major issue in compile, which was resolved with --no-check. |
oh I see I have to admit my mistake here |
@yazan-abdalrahman please check the video that I provided , it shows this error
(this seems a very interesting thing as to why it shows this error ) |
That is the mentioned issue and his solution; I can't understand what a current issue, can provide further details. Recording.2024-10-15.160329.mp4 |
instead of deno compile build/server/index.js , you have to try deno compile --no-check build/index.js for it to have web app also also , even when you do that it shows an error on the first reload probably related to how deno runtime probably gets loaded into tmp for the first time |
Also a minor nitpick for which I am not sure deserves a full issue is currently we need to use https://github.com/pluvial/svelte-adapter-deno or something along this line & change svelte.config.js because the svelte-adapter-auto doesn't have a default runtime for deno , but this only adds friction I suppose , maybe with deno 2.0 , we can get automatic support for deno in sveltekit? |
Sorry, I couldn't find any errors; maybe I misunderstood your requirements, but I believe you had an issue that was not caused by Recording.2024-10-15.161826.mp4We should mention deno member; it will be more helpful in clarifying the situation. |
This comment was marked as off-topic.
This comment was marked as off-topic.
I have the same issue as @yazan-abdalrahman I do the build, but when I run |
I haven't tested it, but there's a chance it might be fixed in canary ( Edit: actually, looking at the reproduction probably not. |
ok, the problem was that we had to compile the I also had to add a couple settings, like this: $ deno compile --no-check --output server --allow-env --allow-net --unstable-node-globals build/index.js
$ ./server
Listening on 0.0.0.0:3000 but when I browse the page I get a $ curl -v localhost:3000
* Trying 127.0.0.1:3000...
* Connected to localhost (127.0.0.1) port 3000 (#0)
> GET / HTTP/1.1
> Host: localhost:3000
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< vary: Accept-Encoding
< transfer-encoding: chunked
< date: Sat, 23 Nov 2024 06:17:56 GMT
<
* Connection #0 to host localhost left intact
handler is not a function |
Here I'll try to document every step taken to ease reproduction $ deno run -A --reload npm:sv create sveltekit-deno-app
$ deno run -A --reload npm:sv create sveltekit-deno-app
┌ Welcome to the Svelte CLI! (v0.6.5)
│
◇ Which template would you like?
│ SvelteKit demo
│
◇ Add type checking with Typescript?
│ Yes, using Typescript syntax
│
◆ Project created
│
◇ What would you like to add to your project? (use arrow keys / space bar)
│ prettier, eslint
│
◇ Which package manager do you want to install dependencies with?
│ None
$ cd sveltekit-deno-app/
$ deno install --allow-scripts=npm:@sveltejs/[email protected]
$ deno run dev (works ok)
$ deno install npm:svelte-adapter-deno update svelte.config.js // import adapter from '@sveltejs/adapter-auto';
import adapter from 'svelte-adapter-deno';
import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';
[...] $ deno run build
$ deno compile --no-check --output server --allow-env --allow-net --unstable-node-globals build/index.js
$ ll -h server
-rwxr-xr-x 1 sas sas 174M Nov 23 15:51 server*
$ ./server
Listening on http://0.0.0.0:3000 And I get this: it seems like all the assets are not being found If I run it like this: $ deno run --allow-env --allow-read --allow-net build/index.js
Listening on http://0.0.0.0:3000 it works ok so it must be a problem with the compile command |
Hmm very interesting , I tried to do what I had done earlier to get it to working and I also have gotten this same issue My interest has been piqued once again. (I was so close to closing this issue) It is showing this in the logs which made me realise that this might be the fault of the compiler and not the adapter https://github.com/pluvial/svelte-adapter-deno because I thought that the adapter hadn't been made compatible with the 5.0 release , but this error points to some compile issue Error: Not found: / |
Another thing to note is that deno doesn't work with the default database / authentication (lucia) example provided by sveltekit because sqllite node remapping isn't done or an error like this was shown , but I think it belongs in different issue |
Same issue here, unable to fetch assets / css files |
Version: deno 2.0.0 (stable, release, x86_64-unknown-linux-gnu) (archlinux)
v8 12.9.202.13-rusty
typescript 5.6.2
Running
deno compile
on a sveltekit app returns aModule not found runtime/control.js
error.Steps to reproduce
deno -A npm:create-svelte@latest my-app
1.1. Click on Sveltekit demo app
1.2. Yes using typescript syntax
1.3. Selecting all the 5 options presented in the next step using space bar ) (Add eslint , prettier , vitest etc.)
cd my-app
deno install
deno run dev
(shows the expected sveltekit demo app at localhost:5173)deno install npm:svelte-adapter-deno
svelte.config.js
file to use Deno adapter:deno run build
to produce build folder and then cd into it (interestingly the last time I ran this it produced a mod.ts file but this time it didn't produce mod.ts I am not exactly sure what has changed since the last time) (this is extremely weird)deno compile build/server/index.js
Output:
error: Module not found "file:///home/test/Projects/deno/my-app/build/runtime/control.js". at file:///home/test/Projects/deno/my-app/build/server/index.js:1345:23
The text was updated successfully, but these errors were encountered: