You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other typescript project dependencies such as uuid, moment, etc seem to work out of the box no problem. But whenever running tests with this import we get the error provided in the description above :
Cannot find module 'driver-license-validator' from 'src/lib/foo.js'.
Note: This is a new addition to a legacy javascript project that's been around for some time. The library works and executes at run time, so this seems to be purely an issue with path resolution in jest - but for the life of me I can't find a difference to indicate why we can't resolve on this dependency alone during the test lifecycle. Hoping you guys might have some experience running in to this type of issue or maybe some insight on if we have misconfigured something.
The text was updated successfully, but these errors were encountered:
Type
What kind of issue is this?
Description the Issue
Cannot find module 'driver-license-validator' from 'src/lib/foo.js'
Steps to Reproduce
npm install driver-license-validator --save
import { isValid } from 'driver-license-validator';
npm run test
Other Information
Jest configuration is basic with no advanced setup or custom jest configuration, just the following sonar integration in package.json
Other typescript project dependencies such as uuid, moment, etc seem to work out of the box no problem. But whenever running tests with this import we get the error provided in the description above :
Cannot find module 'driver-license-validator' from 'src/lib/foo.js'.
Note: This is a new addition to a legacy javascript project that's been around for some time. The library works and executes at run time, so this seems to be purely an issue with path resolution in jest - but for the life of me I can't find a difference to indicate why we can't resolve on this dependency alone during the test lifecycle. Hoping you guys might have some experience running in to this type of issue or maybe some insight on if we have misconfigured something.
The text was updated successfully, but these errors were encountered: