Skip to content
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

Error conflict: 2 packages handling *.html #9

Closed
SteeveFong opened this issue Sep 28, 2015 · 5 comments
Closed

Error conflict: 2 packages handling *.html #9

SteeveFong opened this issue Sep 28, 2015 · 5 comments

Comments

@SteeveFong
Copy link

An error is preventing startup on meteor run:
While determining active plugins: error: conflict: two packages included in the app (barbatus:angular2 and templating) are both trying to handle *.html

Using meteor v1.2.0.1 and meteor-angular2 v0.2.0

@SteeveFong SteeveFong changed the title Error 2 packages handling *.html Error: 2 packages handling *.html Sep 28, 2015
@SteeveFong SteeveFong changed the title Error: 2 packages handling *.html Error conflict: 2 packages handling *.html Sep 28, 2015
@MilosStanic
Copy link

yes, I resolved this by removing the blaze-html-templates package

@SteeveFong
Copy link
Author

Thanks MilosStanic,

I'll leave it open as i think the meteor2-angular package should only handle *.ng.html rather than *.html files.

@barbatus
Copy link
Collaborator

@Stivfk
I think it’s a conceptual shift here. While Blaze is a great UI package, it’s not part of Meteor’s core.
The point here - we want to make use of Blaze patterns in this Angular2 package, but, at the same, let Angular2 to be the main UI library with .html-files devoted to Angular2 as it happens in a regular (not Meteor) Angular2 app.

We could actually let Blaze along, but Meteor’s file processing is not a pipeline today.
I guess, it’ll become so in future versions and one be able to use two HTML processors at the same time.

@SteeveFong
Copy link
Author

That's great. I like the way this is going.

@Urigo
Copy link
Owner

Urigo commented Dec 17, 2015

@barbatus is right, we want to use Angular 2.0 as the main view layer for those who want to.
But we also want to let Blaze developers to migrate gradually to it so we are starting to work on it and on a migration tutorial from Blaze to Angular 2.0.
We would love some help with that, @Stivfk you can join can join the discussion here: #14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants