-
Notifications
You must be signed in to change notification settings - Fork 12k
Webpack cannot find module #2632
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
Comments
Hm, it sounds like the |
This causes it to complain about the classes in the module, rather than the module itself.
From what I can see here, they do appear to be declaring the module in their typings. Appreciate the help. |
@samalexander Im pretty sure the @npm/types for pixi are different to the types you linked.
This was taken from pixijs-userland/pixi-typescript#72 (comment) Just from a quick look at the source, the npm version declares a class and the pixi-typescript version declares a module. |
@GeorgeA93 well spotted, hadn't realised the @types typings weren't the same as those in the PixiJS repo. Manually including the typings file and referencing in src/typings.d.ts file resolves the issue. Closing since this is not an issue with the angular-cli. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
macOS Sierra (version 10.12)
Versions.
angular-cli: 1.0.0-beta.17
node: 4.4.7
os: darwin x64
Repro steps.
The log given by the failure.
Mention any other details that might be useful.
This seems to be a transient error since the example code runs correctly in the browser once webpack has finished generating the bundle.
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: