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 Apr 8, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
I'll update and setup a PR in the next few days once everything is implemented / tested and published. Still need to iron out a few kinks, you can track PR angular/universal#524 if you'd like. Sorry for the delay!
There are still a few outstanding issues we're facing before being able to publish the rc5/6 version of Universal (which will set us up to be prepared for the 1.0 release which is coming shortly as well (but it has no breaking changes thank god!)
The moment we publish Universal I'll refactor and update :)
Now that Angular 2 finally officially released yesterday, i'm really looking forward update. The whole build pipeline with these next generation javascript frameworks are ridiculously complex. I love that this project template gives you a way to hit the ground running.
Working on it now :) @hheexx
There might be some issues (from a Universal point of view) why I was waiting until we ironed out all of the kinks. But if anything Universal-related shows up, you can open up an issue at: https://github.com/angular/universal/issues or let me know here so I can take a look!
Thanks for the update @MarkPieszak. I'm in no hurry but monitoring when everything is up to date. I'm actually still on RC2 for my stuff since I decided to hold when things were in flux. The template has been a great benefit to have and keep up the good work!
@ptk86 - It is updated and published to NPM as of about 30 minutes ago. You can update your generator by running npm install -g generator-aspnetcore-spa.
Reacted by Fergal Moran, GregoryKhakov, Daniel Zuidinga, Dan Ford, Quinntyne Brown, ptk86 and Andrew Temple
Not sure if someone tried the latest NPM or not. With all the defaults and even running webpack commands manually, when trying to run the application using VS it's not working.
Also it would be great if somebody can explain how the template is working( what all parts it has and the reason ) for newbies. Otherwise this all looks black box to someone who is coming from Asp.Net background.
Make sure you first have the following installed npm install -g yo generator-aspnetcore-spa npm install -g webpack
Then create a new directory cd some-empty-directory
Then run the following to create the project in the new folder yo aspnetcore-spa
Then run this command to serve the app dotnet run
Also, make sure you have the latest DotNetCore 1.0.1. I had 1.0.0, and when running dotnet run I received warning messages that it was required to have 1.0.1 installed.
Make sure to have Node 4.x installed, because else to-string loader will break.
Update Node simply with the Windows installer: https://nodejs.org/en/download/
And make sure to call webpack atleast once before dotnet run.
Performed a generator install a few days ago without a hitch.
Now today when an NPM install occurs on a new generator run (clean directory) core-js no longer comes down... in addition to a few other discrepancies in node_modules.
Problem is in Visual Studio Intellisense is not recognizing 'require' and 'Promise'. I believe core-js was filling this void.
Performed a generator install a few days ago without a hitch.
Now today when an NPM install occurs on a new generator run (clean
directory) core-js no longer comes down... in addition to a few other
discrepancies in node_modules.
Problem is in Visual Studio Intellisense is not recognizing 'require' and
'Promise'. I believe core-js was filling this void.
Maybe the update to Typescript 2 had something to to with it? I remember I
recently found an issue that pointed me to removing core-js completely. I
think it was angular universal, that brings its own polyfills.
Any help would be appreciated. I'm finding node, npm, day to day versioning and dependency changes, etc. hard to deal with when all I want is something that works out of the box...
As long as I don't update specific packages, I can roll with the node_modules installed a few days ago. So no rush except I'm sure others will run into issues like I am and a solution somewhere would be beneficial.
EDIT:
I'm using Node 4.x as advised but noticing @types is targeting 6.x?? Unless I'm misunderstanding.
Yes actually Steve we need to move the ts config back to root, almost forgot it can't go "down" directories when looking for @types or anything, just like packagejson webpack, they all need to be in the root 😓
Activity
danjford commentedon Aug 12, 2016
They'll probably have to wait for Angular2-universal to update as well as there are breaking changes with Angular2 RC5. Here is their RC issue.
MarkPieszak commentedon Aug 12, 2016
Yes it's still a work in progress, the changes created quite a ripple effect in Universal. It's a top priority though!
MarkPieszak commentedon Aug 29, 2016
I'll update and setup a PR in the next few days once everything is implemented / tested and published. Still need to iron out a few kinks, you can track PR angular/universal#524 if you'd like. Sorry for the delay!
doczoidberg commentedon Sep 1, 2016
RC6 is around the corner. maybe rc5 should be skipped?
MarkPieszak commentedon Sep 1, 2016
Rc6 shipped last night, I'll update it to that when we figure everything out. :) shouldn't be long this time. Assuming it works with everything ;)
lydemann commentedon Sep 5, 2016
@MarkPieszak What is the status on the rc6 update?
MarkPieszak commentedon Sep 7, 2016
There are still a few outstanding issues we're facing before being able to publish the rc5/6 version of Universal (which will set us up to be prepared for the 1.0 release which is coming shortly as well (but it has no breaking changes thank god!)
The moment we publish Universal I'll refactor and update :)
You can live-track the things remaining here if you'd like:
angular/universal#511 (comment)
[-]Update to Angular2 RC5[/-][+]Update to Angular2 RC6[/+]MarkPieszak commentedon Sep 13, 2016
@SteveSandersonMS
So we finally have things more fine tuned and I'll update to rc7 by Friday! 😀
[-]Update to Angular2 RC6[/-][+]Update to Angular2 Final[/+]vandensd commentedon Sep 16, 2016
Looking forward to the updates! Will the yo Generator update as well with all the goodies?
MarkPieszak commentedon Sep 16, 2016
Sure will, Steve's generator uses the templates inside the repo itself, so it will all be there :)
mikelunn commentedon Sep 16, 2016
Now that Angular 2 finally officially released yesterday, i'm really looking forward update. The whole build pipeline with these next generation javascript frameworks are ridiculously complex. I love that this project template gives you a way to hit the ground running.
hheexx commentedon Sep 16, 2016
Aungular-universal was also updated yesterday.
No show stoppers for updating templates now.
MarkPieszak commentedon Sep 16, 2016
Working on it now :) @hheexx
There might be some issues (from a Universal point of view) why I was waiting until we ironed out all of the kinks. But if anything Universal-related shows up, you can open up an issue at: https://github.com/angular/universal/issues or let me know here so I can take a look!
4 remaining items
vandensd commentedon Sep 18, 2016
Thanks for the update @MarkPieszak. I'm in no hurry but monitoring when everything is up to date. I'm actually still on RC2 for my stuff since I decided to hold when things were in flux. The template has been a great benefit to have and keep up the good work!
ptk86 commentedon Sep 21, 2016
Is the aspnetcore-spa generator updated to Angular2 1.0? I reinstalled it and it still produces Angular 2 2.0.0-rc.4. Could you help?
SteveSandersonMS commentedon Sep 21, 2016
Now done :)
@ptk86 - It is updated and published to NPM as of about 30 minutes ago. You can update your generator by running
npm install -g generator-aspnetcore-spa.doczoidberg commentedon Sep 21, 2016
thanks for your great work!
tanwarsatya commentedon Sep 21, 2016
Not sure if someone tried the latest NPM or not. With all the defaults and even running webpack commands manually, when trying to run the application using VS it's not working.
Also it would be great if somebody can explain how the template is working( what all parts it has and the reason ) for newbies. Otherwise this all looks black box to someone who is coming from Asp.Net background.
This is a good example of explanation.
https://github.com/damienbod/Angular2WebpackVisualStudio
mikelunn commentedon Sep 21, 2016
@tanwarsatya This blog post has some good information about what the repository has to offer:
angular2-react-knockout-apps-on-aspnet-core
Make sure you first have the following installed
npm install -g yo generator-aspnetcore-spanpm install -g webpackThen create a new directory
cd some-empty-directoryThen run the following to create the project in the new folder
yo aspnetcore-spaThen run this command to serve the app
dotnet runAlso, make sure you have the latest DotNetCore 1.0.1. I had 1.0.0, and when running dotnet run I received warning messages that it was required to have 1.0.1 installed.
MJomaa commentedon Sep 23, 2016
@tanwarsatya
Make sure to have Node 4.x installed, because else to-string loader will break.
Update Node simply with the Windows installer: https://nodejs.org/en/download/
And make sure to call
webpackatleast once beforedotnet run.vandensd commentedon Sep 30, 2016
@SteveSanderson
Performed a generator install a few days ago without a hitch.
Now today when an NPM install occurs on a new generator run (clean directory) core-js no longer comes down... in addition to a few other discrepancies in node_modules.
Problem is in Visual Studio Intellisense is not recognizing 'require' and 'Promise'. I believe core-js was filling this void.
colltoaction commentedon Sep 30, 2016
I think it's actually @types/node, but check for yourself :)
On Fri, Sep 30, 2016, 00:51 Steve notifications@github.com wrote:
vandensd commentedon Sep 30, 2016
@tinchou
Agree this is the correct typings file and maybe core-js is not the factor...
However, VS (Enterprise 2015 Update 3)
Intellisense was non issue running generator a few days ago
Today it is
Interested in knowing what the solution might be
colltoaction commentedon Sep 30, 2016
Maybe the update to Typescript 2 had something to to with it? I remember I
recently found an issue that pointed me to removing core-js completely. I
think it was angular universal, that brings its own polyfills.
I can look it up tomorrow if you don't find it.
On Fri, Sep 30, 2016, 01:26 Steve notifications@github.com wrote:
vandensd commentedon Sep 30, 2016
@tinchou
Any help would be appreciated. I'm finding node, npm, day to day versioning and dependency changes, etc. hard to deal with when all I want is something that works out of the box...
As long as I don't update specific packages, I can roll with the node_modules installed a few days ago. So no rush except I'm sure others will run into issues like I am and a solution somewhere would be beneficial.
EDIT:
I'm using Node 4.x as advised but noticing @types is targeting 6.x?? Unless I'm misunderstanding.
hheexx commentedon Sep 30, 2016
I had the same problem and solved it by moving tsconfig from ClientApp to root.
MarkPieszak commentedon Sep 30, 2016
Yes actually Steve we need to move the ts config back to root, almost forgot it can't go "down" directories when looking for @types or anything, just like packagejson webpack, they all need to be in the root 😓