Modernizr: Module not found: Error: Cannot resolve module 'ModernizrProto'

Created on 16 Jun 2016 · 11Comments · Source: Modernizr/Modernizr

Hi,

I'm calling modenizr via webpack and I keep getting this error

ERROR in ./~/modernizr/src/modernizr.js
Module not found: Error: Cannot resolve module 'ModernizrProto' in (path to modernizr)

I can see that ModernizrProto.js is there.

Can anyone help?

Source

ashbryant

👍1

Most helpful comment

@buley I'd suggest using the npm builder we offer at modernizr.com

npm install https://modernizr.com/download?ambientlight-batteryapi-webp-setclasses --save

patrickkettner on 31 Oct 2016

👍13

All 11 comments

hey @ashbryant what is it you are calling? your build? the moderizr module?

patrickkettner on 23 Jun 2016

ping @ashbryant

patrickkettner on 4 Jul 2016

@patrickkettner Sorry, I've been away.

It's in node_modules/modernizr/src/modernizr.js

ashbryant on 5 Jul 2016

no worries!

So that is actually probably not what you want. That is the base file that the modular build is built around. Have you created the build of modernizr that you want?

patrickkettner on 5 Jul 2016

I ran into this issue as well. The reason I'm using the basefile is that the uglification and optimization processes seem to prefer raw base files. I was hoping to build from npm source in a repeatable way. Now planning to do a manual build instead.

buley on 31 Oct 2016

@buley I'd suggest using the npm builder we offer at modernizr.com

npm install https://modernizr.com/download?ambientlight-batteryapi-webp-setclasses --save

patrickkettner on 31 Oct 2016

👍13

Thanks for the link @patrickhlauke. Although your method works, I'm wondering if you can make the npm verion of the library usable as well. The problem with the non-npm package source is that the app now depends on the availability of your website and the network. Installing modernizr in a CI scripts feels potentially slower and riskier because of talking to an additional website.

How feasible would it be to fix the npm package for webpack? I guess everyone will be happy to import Modernizr from 'modernizer/some/extra/path' or import Modernizr from 'modernizer-webpack' if needed.

kachkaev on 11 Jul 2017

i'm assuming you meant @patrickkettner and not me ... confused me there for a second

patrickhlauke on 11 Jul 2017

😄3

Ah sorry!

2 @patrickkettner: Just tried your method and got this in package.json / package-lock.json:

    "Modernizr": "https://modernizr.com/download?ambientlight-batteryapi-webp-setclasses",

    "Modernizr": {
      "version": "https://modernizr.com/download?ambientlight-batteryapi-webp-setclasses",
      "integrity": "sha1-vQBWX2FvDUyoLiZ0fGK2P1n6Rqc="
    },



md5-7713a92f1931d1db21003e8a2152df0f



npm ERR! code EINTEGRITY
npm ERR! sha1-vQBWX2FvDUyoLiZ0fGK2P1n6Rqc= integrity checksum failed when using sha1: wanted sha1-vQBWX2FvDUyoLiZ0fGK2P1n6Rqc= but got sha1-33GogvH/vyMjWkqrGcO8EGvrDps=. (30208 bytes)

i'll probably move Modernizr into src for now – fetching npm packages not from an npm registry feels like a bad idea.

kachkaev on 12 Jul 2017

@kachkaev all that is happening is your lock file is being invalidated because of package changes. thats the point of the lock file. You just need to delete the lock file to upgrade your modernizr package.

patrickkettner on 28 Jul 2017

It be awesome to programmatically use Modernize with ease -- I don't want it on the window, I don't want it to touch the document.documentElement.

I got it to work with mapping all the named modules and trying to figure out how to implement this dynamically in the future.

My use case:
Attempting to make all my Component classes standalone and able to add their own specific detects per Components' use-cases. Encapsulate and modularize all the things!