Open togakangaroo opened 9 years ago
jspm 0.16 stable is out and should be used with karma-jspm 2.0 (stable, non-beta). Could you try it out with the stable releases and see if you experience the same issue?
@maxwellpeterson-wf huh...just reverted everything, blew away both node_modules and jspm_packages, and updated to karma-jspm 2.0.1 and its still 404ing.
Investigating what changed...I was running tests this morning
Ok, so jumped to a branch that I know works and starting there.
jspm
to 0.16.1
from 0.15.5
karma-jspm
to 2.0.1
from 1.1.5
WARN [watcher]: Pattern "W:\MyApp\Scripts\jspm_packages\system-polyfills.src.js" does not match any file.
INFO [karma]: Karma v0.12.37 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 44.0.2403 (Windows 8.1 0.0.0)]: Connected on socket W6No3J-IWcl1o6ldVgXo with id 79750515
WARN [web-server]: 404: /Scripts/tests/adminArea.specs.js
WARN [web-server]: 404: /Scripts/tests/doctor-list.specs.js
WARN [web-server]: 404: /Scripts/tests/inline-editable-grid.specs.js
WARN [web-server]: 404: /Scripts/tests/listEditor.specs.js
WARN [web-server]: 404: /Scripts/tests/listStores.specs.js
WARN [web-server]: 404: /Scripts/tests/react-helpers.specs.js
WARN [web-server]: 404: /Scripts/tests/utilities.specs.js
WARN [web-server]: 404: /Scripts/tests/validation.specs.js
Chrome 44.0.2403 (Windows 8.1 0.0.0) ERROR: 'Potentially unhandled rejection [5] Error loading "tests/adminArea.specs" at http://localhost:9876/Scripts/tests/adminArea.specs.js
Not Found: http://localhost:9876/Scripts/tests/adminArea.specs.js (WARNING: non-Error used)'
WARN [Chrome 44.0.2403 (Windows 8.1 0.0.0)]: Disconnected (1 times), because no message in 10000 ms.
Finished in 10.55 secs / 0 secs
Note the first error occurs before karma even opens! That file doesn't exist btw
> ls "W:\MyApp\Scripts\jspm_packages\"
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 2015-08-25 2:14 PM <DIR> github
d---- 2015-08-25 2:15 PM <DIR> npm
-a--- 2015-08-25 2:15 PM 15 .loaderversions
-a--- 2015-08-25 2:15 PM 30234 es6-module-loader.js
-a--- 2015-08-25 2:15 PM 42423 es6-module-loader.js.map
-a--- 2015-08-25 2:15 PM 81455 es6-module-loader.src.js
-a--- 2015-08-25 2:15 PM 25562 system.js
-a--- 2015-08-25 2:15 PM 36355 system.js.map
-a--- 2015-08-25 2:15 PM 73305 system.src.js
Update: I've been playing around with this (jumping around in my history, clearing out npm, jspm, etc) and just hit a situation where jspm and karma-jspm both are on the latest stable as above, but that first module-loader error no longer happens. The 404 errors still occur though
I have the following config file
All my tests (In
/Scripts/tests/*.specs.js
) worked fine on previous karma-jspm versions. But as of updating jspm to beta.3 (necessary to address this issue) I hit the karma-jspm baseUrl error. So I tried updating karma-jspm to2.0.1-beta.2
but now all routes to all scripts (specs and regular, loaded via Systemjs or directly via the url bar) are 404'ing.