Skip to content
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.

Conflict with templating packages #37

Open
gbisheimer opened this issue Jan 2, 2016 · 4 comments
Open

Conflict with templating packages #37

gbisheimer opened this issue Jan 2, 2016 · 4 comments
Assignees

Comments

@gbisheimer
Copy link

When include your package in my project I get this error:

error: conflict: two packages included in codefights:blaze-material-ui (templating and peerlibrary:blaze-components) are both trying to handle *.html

Which is related to this issue in meteor-blaze-components

Is the templating package really needed?

Thanks!

@mitar
Copy link

mitar commented Jan 2, 2016

With new version of Blaze Components it is not anymore, because it is provided through Blaze Components.

@pixelass
Copy link
Contributor

pixelass commented Jan 6, 2016

I had the same issue when trying something else. I will try to migrate to the new blaze components but I am already working on a new more reactive implementation of this lib so time is rare.

@pixelass pixelass self-assigned this Jan 6, 2016
@pixelass
Copy link
Contributor

pixelass commented Jan 6, 2016

@gbisheimer do you know how to add a local package? If yes you can try this branch https://github.com/Code-Fights/blaze-material-ui/tree/bug/fix-deps

It removes templating and some other leftover meteor 1.1.x stuff. I ran a few tests and could not find any issues. The blaze component version is still 0.14.0 so I'm hoping you don't run into issues due to that.

If you need help on local packages I can suggest mgp which lets you install directly from git : https://github.com/DispatchMe/mgp. We use it a a lot for private packages.

If you need any help just ask.
Merging and releasing on atmosphere as soon as you can confirm this as resolved.

@gbisheimer
Copy link
Author

@pixelass, I already forked this repo and removed the dependency from templating package from package.js file. I had no problems with that so far and it's working as expeted.

Thanks for the mgp suggestion. Will try it out.

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

No branches or pull requests

3 participants