Repository navigation
upgrade blueprints to 2.0.0-alpha.47 #84
Description
- package.json needs to be updated (we intentionally bump the version manually each time for now to have control over breaking changes that require blueprints update)
- replace
import ... from 'angular2/angular2'with... from 'angular2/core'(this might still change in the future, see update typings entry point in npm's package.json angular#5539, but for now let's switch tocore) - the only exception to the above is
bootstrapwhich should come fromimport {bootstrap} from 'angular2/platform/browser'
that should be it...
cc: @wardbell for documentation update since that will be affected in similar way
Metadata
Metadata
Assignees
Labels
No labels
Activity
IgorMinar commentedon Dec 2, 2015
Anyone wants to work on this?
cironunes commentedon Dec 2, 2015
Can I assign to me?
IgorMinar commentedon Dec 2, 2015
sure
On Tue, Dec 1, 2015 at 5:16 PM Ciro Nunes notifications@github.com wrote:
Brocco commentedon Dec 2, 2015
@cironunes if not you're busy, this is something that I'm more than willing to take on
cironunes commentedon Dec 2, 2015
I'm getting many errors from TypeScript, I think that they are related to typings.
I noticed that there's a breaking change regarding typings. Is it supposed to break?
cironunes commentedon Dec 2, 2015
I mean, aren't we already using typings from the package?
IgorMinar commentedon Dec 2, 2015
We are. It should work just fine. I tested a generated app locally with 47
and it bootstrapped without errors. I haven't tested anything else though.
On Tue, Dec 1, 2015 at 5:56 PM Ciro Nunes notifications@github.com wrote:
Brocco commentedon Dec 2, 2015
@IgorMinar was that a TypeScript project?
cironunes commentedon Dec 2, 2015
Forget about it. It's working fine.
chore: update blueprints to 2.0.0-alpha-47
chore: update blueprints to 2.0.0-alpha-47
docs(testing): upgrade imports to 2.0.0-alpha-48
angular-automatic-lock-bot commentedon Sep 5, 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.