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

Use with 3rd party component libraries #40

Open
nikolasleblanc opened this issue Nov 14, 2016 · 4 comments
Open

Use with 3rd party component libraries #40

nikolasleblanc opened this issue Nov 14, 2016 · 4 comments

Comments

@nikolasleblanc
Copy link

Hey @TheLarkInn, quick question for you, we're developing a component library with angular 2 that is then consumed by angular 2 applications.

Is angular2-template-loader capable of digging into the component files of such a library and swapping out its templateUrls and styleUrls just as it does the consuming application, provided everything's getting pulled in by webpack (which it is)?

Let me know if I can clarify my question for you.

Thanks.

@TheLarkInn
Copy link
Owner

It is however the stipulation is that you would need to have the libraries ts src available. This loader should be able to load js transpiled but I have seen issues with this in the past, would be open to merging a PR that supports this.

@alvaro9210
Copy link

alvaro9210 commented Mar 15, 2017

Hey, is there a way to use this loader with third party libraries?
Or is just a no go for third party libraries with angular?
Also I think my opened, now closed, issue #48 shouldn't be closed. Because it's related to this incompatibility with third party libraries with this loader.

I've also made this question in Stackoverflow.
http://stackoverflow.com/questions/42816079/webpack-is-not-resolving-extensions-from-third-party-libraries

@nikolasleblanc
Copy link
Author

http://stackoverflow.com/questions/42816079/webpack-is-not-resolving-extensions-from-third-party-libraries/42817176#42817176

Been there, gave you a response in SO.

@alvaro9210
Copy link

The answer of @nikolasleblanc works like a charm!!
Just take in mind that this wouldn't work with lazy loaded routes in you library.

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

No branches or pull requests

3 participants