-
Notifications
You must be signed in to change notification settings - Fork 70
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
404 when loading templates from npm linked dependencies #48
Comments
Hello, I have the same problem with loading component templates on version 0.6.1 version (pushed 2 hours ago) and I downgraded to 0.6.0 and locked it and problem fixed.
|
Hi - I seem to be having the exact same issue with my components, I locked the version to 0.6.0 for now :) |
Same problem in one of our projects. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currently developing an Angular 2 project (Let's call it Workbench) which dependes on another Angular 2 project (Let's call it Panel).
Panel provides of a lot of components which are then used in Workbench.
At the same time I am developing Workbench, I make changes to Panel, so I need to view the changes immediately and that's why I linked the dependency with npm link (
npm link ../panel/dist
) and after that Panel is being found by my bundler (Webpack 2) and its bundled correctly.Until here everything works fine, the problem comes when the browser loads the Workbench app because it doesn't find the templates of the components provided by the Panel component, it throws a
404 - Error Message
.Here's a screenshot of the error messages:
As you can see, the
angular2-template-loader
is trying to resolve the templates by going to the src folder of the Workbench app, not the panel app. (http://127.0.0.1:8080/src/header.component.html
)Here's how I import the templates and styles of the components of Panel.
And these are the Webpack rules for resolving file extensions:
Is it possible to have linked packages using
angular2-template-loader
?The text was updated successfully, but these errors were encountered: