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

Webpack: 3rd Party module not found, but functional #1513

Closed
itsJess1ca opened this issue Aug 2, 2016 · 4 comments
Closed

Webpack: 3rd Party module not found, but functional #1513

itsJess1ca opened this issue Aug 2, 2016 · 4 comments

Comments

@itsJess1ca
Copy link

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
    Windows 10
  2. Versions. Please run ng --version. If there's nothing outputted, please run
    in a Terminal: node --version and paste the result here:
    local (v1.0.0-beta.10, branch: master)
  3. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
  • App created with webpack cli built from master.
  • Ran npm install lodash --save,
  • imported lodash into my component with import * as _ from 'lodash';
  • proceeded to use lodash functions (_.forIn() in this case)
  1. The log given by the failure. Normally this include a stack trace and some
    more information.
    Cannot find module 'lodash' .
  2. Mention any other details that might be useful.
    I haven't noticed this with other libs I'm using, including material2 and ngrx/store.

Thanks! We'll be in touch soon.

@zackarychapple
Copy link
Contributor

I had better luck with "@types/lodash": "^4.0.26-alpha" and using the same import.

@itsJess1ca
Copy link
Author

Ok so installing @types/lodash as well resolved the issue - though If possible a better error message would be nice here.

Something like Couldn't find types for module 'lodash'

@elpddev
Copy link

elpddev commented Aug 3, 2016

Same here. I have created a custom type definition for a 3rd party library and then the error was gone. The error message is not clear.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
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