You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
Last week, I started a side POC getting universal run on Java 8 Nashorn. And I discovered that SystemJS is not supported on Nashorn. I opened an issue for that.
See it here: systemjs/systemjs#1113
This issue description is vague, but I can say I had universal running against systemjs (without jspm) in the past https://github.com/sullivanpt/ng2-universal-seed/tree/systemjs. (I abandoned the branch because webpack/browserify gave a more consistent dependency experience on express.)
Build error
{ Error on fetch for node_modules/angular2-universal/dist/common.js at file:///Users/alex/Sites/ng2/sampleTSexpress/universal-systemjs/node_modules/angular2-universal/dist/common.js
Loading node_modules/angular2-universal/dist/browser/browser.js
Loading node_modules/angular2-universal/browser.js
Loading dist/client.js
Error: ENOENT: no such file or directory, open '/Users/alex/Sites/ng2/sampleTSexpress/universal-systemjs/node_modules/angular2-universal/dist/common.js'
at Error (native)
originalErr:
{ Error: ENOENT: no such file or directory, open '/Users/alex/Sites/ng2/sampleTSexpress/universal-systemjs/node_modules/angular2-universal/dist/common.js'
at Error (native)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/Users/alex/Sites/ng2/sampleTSexpress/universal-systemjs/node_modules/angular2-universal/dist/common.js' } }
The above sounds like a standard Node compatibility problem - trying to load ../common as a directory require in Node through SystemJS when what is expected by SystemJS is ../common/index.js.
Alternatively this project could rewrite the require('../common') in dist/browser/browser.js to require('../common/index.js') and not explicitly rely on the directory require resolution.
Is there any progress on this? Is there any plan when this will be ready for use? Do you think that SystemJs will be usable with asp.net core server side?
Hi, @kukjevov, so this is still very high on our list, but it is currently not on the critical path for the full release. We have a couple high priority bugs and upgrades we are focused on now. Of course, if anyone from the community wants to help on this, please let @gdi2290 and I know and we can provide some guidance. Otherwise this will be a post-release item.
Thank you very much for answers. I know that there is Webpack already prepared for usage with .NET Core. My reason is simple, right now im using SystemJS and currently dont have time to study WebPack in the first, but dont think this could be problem but dont have time to update project for WebPack.
Still im missing a bit documentation for Universal, when im using something i need to know how it works, not in detail but currently i dont see anywhere how is "index.html" loaded on server side.
But im already thinking about migrating to WebPack.
Anyway thx for replies :)
Activity
wesleycho commentedon Feb 26, 2016
I'll take a look at this
manekinekko commentedon Feb 28, 2016
@jeffwhelpley @wesleycho this may be related...
Last week, I started a side POC getting universal run on Java 8 Nashorn. And I discovered that SystemJS is not supported on Nashorn. I opened an issue for that.
See it here: systemjs/systemjs#1113
guybedford commentedon Mar 7, 2016
Just let me know if I can help here at all as well. Conditional package loading in SystemJS may come in handy here too.
sullivanpt commentedon May 9, 2016
This issue description is vague, but I can say I had universal running against systemjs (without jspm) in the past https://github.com/sullivanpt/ng2-universal-seed/tree/systemjs. (I abandoned the branch because webpack/browserify gave a more consistent dependency experience on express.)
jeffwhelpley commentedon May 9, 2016
Thanks for the feedback @sullivanpt. Hey, @gdi2290 and @manekinekko what were the issues you guys ran into with this?
Codenator81 commentedon May 14, 2016
@jeffwhelpley First when I use systemjs-builder and in systemjs.config.js
and import bootstrap
have error
when build
guybedford commentedon May 15, 2016
The above sounds like a standard Node compatibility problem - trying to load
../commonas a directory require in Node through SystemJS when what is expected by SystemJS is../common/index.js.Alternatively this project could rewrite the
require('../common')indist/browser/browser.jstorequire('../common/index.js')and not explicitly rely on the directory require resolution.kukjevov commentedon Sep 10, 2016
Is there any progress on this? Is there any plan when this will be ready for use? Do you think that SystemJs will be usable with asp.net core server side?
Thank you
jeffwhelpley commentedon Sep 10, 2016
Hi, @kukjevov, so this is still very high on our list, but it is currently not on the critical path for the full release. We have a couple high priority bugs and upgrades we are focused on now. Of course, if anyone from the community wants to help on this, please let @gdi2290 and I know and we can provide some guidance. Otherwise this will be a post-release item.
MarkPieszak commentedon Sep 11, 2016
@kukjevov There's a great webpack starter with .NET Core, any reason you want to use System? Just curious!
kuldeepkeshwar commentedon Sep 11, 2016
@kukjevov
@MarkPieszak is right
it's easy to use and it's a more mature technology compared to its closest competitor, SystemJS.
kukjevov commentedon Sep 11, 2016
Hi all :).
Thank you very much for answers. I know that there is Webpack already prepared for usage with .NET Core. My reason is simple, right now im using SystemJS and currently dont have time to study WebPack in the first, but dont think this could be problem but dont have time to update project for WebPack.
Still im missing a bit documentation for Universal, when im using something i need to know how it works, not in detail but currently i dont see anywhere how is "index.html" loaded on server side.
But im already thinking about migrating to WebPack.
Anyway thx for replies :)
PatrickJS commentedon Oct 13, 2016
I'm going to close this until someone from the community creates a PR to own support of SystemJS
NiklasRaab commentedon Mar 9, 2017
Please provide support for systemjs!
PatrickJS commentedon Mar 9, 2017
universal is merging into core which means it has support in Angular 4+
NiklasRaab commentedon Mar 9, 2017
Love you! Thats properbly the fastest answer i've ever get 👍
PatrickJS commentedon Mar 9, 2017
no problem 👍
angular-automatic-lock-bot commentedon Sep 4, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.