Closed JoeCodeswell closed 8 years ago
Next thing i tried to do was run from the completed es6 clone. Here's the result.
>live-server --open=app
Serving "C:\1d\googlePjs\PWAppsPjs\AngMatPwaShoppingListPj\JoesShoppingListPj\1 AngMat\JoesShoppingListPj\JoesShoppingList" at http://127.0.0.1:8080
GET /app/jspm_packages/github/angular/bower-material@master/angular-material.css 404 3.543 ms - 88
GET /app/jspm_packages/system.js 404 0.706 ms - 40
GET /favicon.ico 404 0.511 ms - 24
So finally, i tried answering the jspm update
with global defaults. i did this in my default user folder.
>jspm update
warn Running jspm globally, it is advisable to locally install jspm via npm install jspm --save-dev.
Package.json file does not exist, create it? [yes]:yes
Would you like jspm to prefix the jspm package.json properties under jspm? [yes]:yes
Enter server baseURL (public folder path) [./]:./baseURLfolder
Enter jspm packages folder [baseURLfolder\jspm_packages]:
Enter config file path [baseURLfolder\config.js]:
Configuration file baseURLfolder\config.js doesn't exist, create it? [yes]:yes
Enter client baseURL (public folder URL) [/]:./clientBaseURLfolder
Do you wish to use a transpiler? [yes]:yes
Which ES6 transpiler would you like to use, Babel, TypeScript or Traceur? [babel]:babel
ok Install tree has no forks.
Looking up loader files...
system.js
system.js.map
system-csp-production.js
system.src.js
system-polyfills.js
system-polyfills.src.js
system-csp-production.js.map
system-polyfills.js.map
system-csp-production.src.js
Using loader versions:
systemjs@0.19.37
Looking up npm:babel-core
Looking up npm:babel-runtime
Looking up npm:core-js
Creating registry cache...
Downloading npm:core-js@1.2.7
Downloading npm:babel-runtime@5.8.38
Downloading npm:babel-core@5.8.38
Looking up github:jspm/nodelibs-process
ok Installed babel as npm:babel-core@^5.8.24 (5.8.38)
Downloading github:jspm/nodelibs-process@0.1.2
Looking up npm:process
Looking up github:jspm/nodelibs-path
Looking up github:jspm/nodelibs-fs
Looking up github:systemjs/plugin-json
Downloading npm:process@0.11.9
ok Installed github:jspm/nodelibs-process@^0.1.0 (0.1.2)
ok Installed npm:process@^0.11.0 (0.11.9)
Downloading github:jspm/nodelibs-path@0.1.0
Looking up github:jspm/nodelibs-assert
Looking up github:jspm/nodelibs-vm
Downloading github:jspm/nodelibs-fs@0.1.2
Looking up npm:path-browserify
Downloading npm:path-browserify@0.0.0
ok Installed npm:path-browserify@0.0.0 (0.0.0)
Downloading github:systemjs/plugin-json@0.1.2
Downloading github:jspm/nodelibs-vm@0.1.0
ok Installed github:jspm/nodelibs-path@^0.1.0 (0.1.0)
Looking up npm:vm-browserify
ok Installed github:jspm/nodelibs-fs@^0.1.0 (0.1.2)
Downloading npm:vm-browserify@0.0.4
Looking up npm:indexof
Downloading github:jspm/nodelibs-assert@0.1.0
Downloading npm:indexof@0.0.1
ok Installed npm:vm-browserify@0.0.4 (0.0.4)
ok Installed npm:indexof@0.0.1 (0.0.1)
Looking up npm:assert
Downloading npm:assert@1.4.1
Looking up npm:util
Downloading npm:util@0.10.3
Looking up npm:inherits
Downloading npm:inherits@2.0.1
ok Installed npm:assert@^1.3.0 (1.4.1)
ok Installed github:systemjs/plugin-json@^0.1.0 (0.1.2)
ok Installed github:jspm/nodelibs-vm@^0.1.0 (0.1.0)
ok Installed npm:util@0.10.3 (0.10.3)
ok Installed npm:inherits@2.0.1 (2.0.1)
Looking up github:jspm/nodelibs-util
ok Installed github:jspm/nodelibs-assert@^0.1.0 (0.1.0)
Downloading github:jspm/nodelibs-util@0.1.0
ok Installed github:jspm/nodelibs-util@^0.1.0 (0.1.0)
Looking up github:jspm/nodelibs-buffer
Downloading github:jspm/nodelibs-buffer@0.1.0
Looking up npm:buffer
Downloading npm:buffer@3.6.0
Looking up npm:base64-js
Looking up npm:ieee754
Looking up npm:isarray
Downloading npm:isarray@1.0.0
Downloading npm:ieee754@1.1.6
Downloading npm:base64-js@0.0.8
ok Installed npm:isarray@^1.0.0 (1.0.0)
ok Installed npm:ieee754@^1.1.4 (1.1.6)
ok Installed npm:base64-js@0.0.8 (0.0.8)
ok Installed npm:buffer@^3.0.1 (3.6.0)
ok Installed github:jspm/nodelibs-buffer@^0.1.0 (0.1.0)
Looking up github:jspm/nodelibs-child_process
Downloading github:jspm/nodelibs-child_process@0.1.0
ok Installed github:jspm/nodelibs-child_process@^0.1.0 (0.1.0)
ok Installed babel-runtime as npm:babel-runtime@^5.8.24 (5.8.38)
ok Installed core-js as npm:core-js@^1.1.4 (1.2.7)
ok Loader files downloaded successfully
ok Install complete.
So AFTER the above, when i tried to run the FINAL tutorial, here's what i got.
>live-server --open=app
Serving "C:\1d\googlePjs\PWAppsPjs\AngMatPwaShoppingListPj\JoesShoppingListPjs\1 AngMat\JoesShoppingListPj\JoesShoppingList" at http://127.0.0.1:8080
GET /app/jspm_packages/github/angular/bower-material@master/angular-material.css 404 5.367 ms - 88
GET /app/jspm_packages/system.js 404 0.504 ms - 40
I'm REALLY not sure how to proceed. Thanks for the help in advance. Love and peace, Joe
I thought I'd also include the console errors from chrome dev tools.
http://127.0.0.1:8080/app/jspm_packages/github/angular/bower-material@master/angular-material.css Failed to load resource: the server responded with a status of 404 (Not Found)
http://127.0.0.1:8080/app/jspm_packages/system.js Failed to load resource: the server responded with a status of 404 (Not Found)
config.js:1 Uncaught ReferenceError: System is not defined
127.0.0.1/:53 Uncaught ReferenceError: System is not defined
127.0.0.1/:84 Live reload enabled.
http://127.0.0.1:8080/favicon.ico Failed to load resource: the server responded with a status of 404 (Not Found)
http://127.0.0.1:8080/app/jspm_packages/github/angular/bower-material@master/angular-material.css Failed to load resource: the server responded with a status of 404 (Not Found)
Thanks.
Love and peace, Joe
@JoeCodeswell Sorry for the delay! I'll try to take a look at this tonight (have to reboot into Windows 10) and see what's up. We do have a package.json
, so it may be a Windows issue getting confused with a capital Package.json
or something like that.
Thanks, Topher. Love and peace, Joe
@JoeCodeswell Apologies for the delay; I totally forgot about doing this. I'll put it on my calendar to do it later today!
@JoeCodeswell Okay, I just looked into this a bit and I'm not having any issues. Can you tell me what version of Node you are using?
Hi Topher.
I am running: node --version v4.3.0 on Microsoft Windows [Version 10.0.14393] Thanks. Love and peace, Joe
@JoeCodeswell Try running it from the windows cli, i had the same issue when i was using git bash. It seems its unable to find the correct resource directory.
@chauhan-rahul Thanks for the info!
@JoeCodeswell Can you test this out and see if it works? I'm going to go ahead and close this issue, but if you are still having trouble, just comment and I'll reopen.
Thanks!
On windows 10, i followed all your instructions but when i got to
jspm update
, there seemed to be a problem.I said no because i wasn't sure where Package.json would be created.
One more comment/question. It would be helpful to me if you defined a beginning directory structure right before Step-1 of the tutorial. So my question is, "Is the unzip of the clone the only thing that's affected by the tutorial instructions?" I ask this question because I am not sure where to put
jspm --save-dev
.Thanks in advance.
Love and peace, Joe