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.

Sign up for GitHub

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

Jump to bottom

Component #1

Open
leostera opened this issue Oct 15, 2013 · 4 comments
Open

Component #1

leostera opened this issue Oct 15, 2013 · 4 comments

Comments

@leostera
Copy link

Hi there! I'd love to have this as a component.io-compatible component.

I could either take care of the port using componentizr but I imagine that this is most likely going to be changing soon, so it didn't hurt to ask :P
@robinboehm
Copy link
Contributor

What I need to do exactly?
Modify this repo with componentizr oder create a fork with this module as component?

componentizr does this automatically for me?

@robinboehm
Copy link
Contributor

@PascalPrecht what do you think?

@0x-r4bbit
Copy link
Contributor

@robinboehm Honestly I don't have any idea what this issue is about. Have to take a look at this component.io stuff. I'll get back to you once I did it.

@0x-r4bbit
Copy link
Contributor

@robinboehm @leostera Ahhh so it turned out its just another package manager right? So basically its all about providing an additional json that specifies the package as a component. So yea, sure we should do that. We also do it for bower. There might be even people who would like to see this package on NuGet. As you can see here, it makes the live of .NET developers much easier angular-translate/angular-translate#210

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@0x-r4bbit @robinboehm @leostera