-
Notifications
You must be signed in to change notification settings - Fork 214
hangs on windows currently #10
Comments
It's not a typo — it's almost as if it thinks It also looks like maybe it's resolving |
Think you're right re. carriage returns @Rich-Harris It was wrapping in places in the output but I wasn't sure if it was my editor! |
This is an issue on Windows 10 as well (probably know that) |
I didn't, but I assumed as much! I'm not really any closer to figuring out what's going on, so if you have any ideas... |
Ok, I've released a new version of Sapper — 0.2 — and the tests appear to be passing in Windows now. Could you try updating please? As well as bumping the version, you'll need to add the following to package.json: "scripts": {
"dev": "node server.js",
+ "build": "sapper build",
"start": "cross-env NODE_ENV=production node server.js",
+ "prestart": "npm run build",
"cy:run": "cypress run",
"cy:open": "cypress open",
"test": "run-p --race dev cy:run"
}, At least then if it still fails we'll be able to figure out if it's a build-time problem or a run-time problem. |
I don't have a lot of time to dig deeper, but if this is still around when I do, Ill try to be a better help. |
@Rich-Harris Re-installed and ran again with your suggested changes to package.json "./.sapper/server-routes.js |
Can you try a couple of things please? Try running "scripts": {
- "dev": "node server.js",
- "build": "sapper build",
- "start": "cross-env NODE_ENV=production node server.js",
+ "dev": "cross-env SAPPER_DEST=testdir node server.js",
+ "build": "cross-env SAPPER_DEST=testdir sapper build",
+ "start": "cross-env NODE_ENV=production SAPPER_DEST=testdir node server.js",
"prestart": "npm run build",
"cy:run": "cypress run",
"cy:open": "cypress open",
"test": "run-p --race dev cy:run"
} ...and try |
(I say that because |
After trying to debug webpack for 1-2 hours I'm feeling quite ill
|
@Rich-Harris, this is the output you were looking for C:\Apps\Testarea\svelte_sapper\my-app>npm run dev
C:\Apps\Testarea\svelte_sapper\my-app>npm run build
|
Ah, so there is a place in the code where it's assuming I've created two branches — could you try installing from these and seeing what happens? yarn add https://github.com/sveltejs/sapper#possible-windows-fix-1 && yarn run build
yarn add https://github.com/sveltejs/sapper#possible-windows-fix-2 && yarn run build (or |
: ( @Rich-Harris Steps I took:
output from (4) - (5 is below) :
output from (5):
|
Ok, I think I have it! Can you try yarn add https://github.com/sveltejs/sapper#possible-windows-fix-3 && yarn run build please? You might also need to set I haven't totally got to the bottom of this, but preliminary investigation suggests webpack is to blame. I don't think it likes absolute |
Looks like you've cracked the main problem! just a tweak required @Rich-Harris
|
Wahoo! The remaining errors are related to the |
so near and yet npx degit sveltejs/sapper-template my-app
listening on port 3000 |
I haven't released the fix yet! So starting from scratch with |
0.2.3 is released, and I've updated the deps in this repo... fingers crossed 🤞 |
Released 0.2.4 which should also fix the HMR stuff, and a new version of svelte-loader which does the same thing for generated CSS files |
Will be testing on holiday. Thanks! |
error at handle_route()
Module not found: Error: Can't resolve 'c:AppsTestareasvelte_sappermyappoutes/about.html' in 'c:\Apps\Testarea\svelte_sapper\myapp.sapper'
Also error messages suggest a typo:
outes rather than routes
"./.sapper/server-routes.js
Module not found: Error: Can't resolve 'c:AppsTestareasvelte_sappermyappoutes/about.html' in 'c:\Apps\Testarea\svelte_sapper\myapp.sapper'
resolve 'c:AppsTestareasvelte_sappermyapp
outes/about.html' in 'c:\Apps\Testarea\svelte_sapper\myapp.sapper'
Parsed request is a module
using description file: c:\Apps\Testarea\svelte_sapper\myapp\package.json (relative path: ./.sapper)
after using description file: c:\Apps\Testarea\svelte_sapper\myapp\package.json (relative path: ./.sapper)
resolve as module
c:\Apps\Testarea\svelte_sapper\myapp.sapper\node_modules doesn't exist or is not a directory
c:\Apps\Testarea\svelte_sapper\node_modules doesn't exist or is not a directory
c:\Apps\Testarea\svelte\node_modules doesn't exist or is not a directory
c:\Apps\Testarea\node_modules doesn't exist or is not a directory
c:\Apps\node_modules doesn't exist or is not a directory
c:\node_modules doesn't exist or is not a directory
looking for modules in c:\Apps\Testarea\svelte_sapper\myapp\node_modules
using description file: c:\Apps\Testarea\svelte_sapper\myapp\package.json (relative path: ./node_modules)
after using description file: c:\Apps\Testarea\svelte_sapper\myapp\package.json (relative path: ./node_modules)
using description file: c:\Apps\Testarea\svelte_sapper\myapp\package.json (relative path: ./node_modules/c:AppsTestareasvelte_sappermyappoutes/about.html)
no extension
c:\Apps\Testarea\svelte_sapper\myapp\node_modules\c:AppsTestareasvelte_sappermyappoutes\about.html doesn't exist
.js
c:\Apps\Testarea\svelte_sapper\myapp\node_modules\c:AppsTestareasvelte_sappermyappoutes\about.html.js doesn't exist
.html
c:\Apps\Testarea\svelte_sapper\myapp\node_modules\c:AppsTestareasvelte_sappermyappoutes\about.html.html doesn't exist
as directory
c:\Apps\Testarea\svelte_sapper\myapp\node_modules\c:AppsTestareasvelte_sappermyappoutes\about.html doesn't exist
[c:\Apps\Testarea\svelte_sapper\myapp.sapper\node_modules]
[c:\Apps\Testarea\svelte_sapper\node_modules]
[c:\Apps\Testarea\svelte\node_modules]
[c:\Apps\Testarea\node_modules]
[c:\Apps\node_modules]
[c:\node_modules]
[c:\Apps\Testarea\svelte_sapper\myapp\node_modules\c:AppsTestareasvelte_sappermyappoutes\about.html]
[c:\Apps\Testarea\svelte_sapper\myapp\node_modules\c:AppsTestareasvelte_sappermyappoutes\about.html.js]
[c:\Apps\Testarea\svelte_sapper\myapp\node_modules\c:AppsTestareasvelte_sappermyappoutes\about.html.html]
[c:\Apps\Testarea\svelte_sapper\myapp\node_modules\c:AppsTestareasvelte_sappermyappoutes\about.html]
@ ./.sapper/server-routes.js 1:0-76"
The text was updated successfully, but these errors were encountered: