-
Notifications
You must be signed in to change notification settings - Fork 37
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
JSPM Bundle not right with systemjs-hot-reloader #130
Comments
@NickPadilla Since |
Closing, if still not working feel free to reopen :) |
@alexisvincent I'm having this problem. I tried with your code without success, because it only bundle to a single file. I'm using v1.1.0. I don't want to modify my code for production either. Any advice? Thanks |
It's suppose to bundle to a single file though? |
Sorry I just read this today. I thought that this command |
Hmm, weird. If you do a string search inside your bundle, can you see the systemjs-hot-reloader library? Are you loading the JSPM config? Sorry this took so long, under a lot of work pressure. |
Is I wonder if you aren't perhaps bundling in production mode and then loading it in development mode. Can you try set both to dev? |
Hello!
Great work on this project, thanks a heap! When i am doing a
jspm bundle base app/base-bundle.js --inject --minify
and i try running that build using the original index.html - i get this error in the console.GET http://localhost:8000/systemjs-hot-reloader 404 (File not found)
N @ fetch.js:32
(anonymous) @ instantiate.js:165
I am just running this using
python -m SimpleHTTPServer
.I was under the impression that systemjs-hot-reloader would get written out during the build, or just providing a stub implementation. If i try to add ta map field in the jspm.browser.js to not load systemjs-hot-reloader then i get an error that
connect()
is not a function.Is there a way to tell the JSPM build to build for production, thought it was the default, so that i don't have to really edit my index.html for production?
The text was updated successfully, but these errors were encountered: