Entry module not found: Error: Can't resolve 'respond.js'

[chrisyue]

I don't know if it's a issue related with encore or webpack，I am new to both.

this error occurs after I add

    .addEntry('for-ie', 'respond.js')

to webpack.config.js

there is no problem when I add some other other libs like html5shiv.

[stof]

how have you installed respond.js ?

[weaverryan]

It looks like Respond.js doesn't advertise their main script properly: scottjehl/Respond#360

Try this instead:

    .addEntry('for-ie', 'respond.js/dest/respond.src.js')
``

This will look in the `node_modules/respond.js` directory, and then look for the `dest/response.src.js` file.

[stof]

Yeah, I think Respond was just not meant to be installed through npm (they are not registered in npmjs.com either)

[chrisyue]

respond.js/dest/respond.src.js is working , thank you guys.

but what does "I think Respond was just not meant to be installed through npm" means? what's going on if I install respond.js with yarn? should I use public cdn or some other way to include respond.js ?

[weaverryan]

My best guess is that this library isn't well maintained (not many commits, no activity on issues or pull requests) - so that's why it doesn't play well with webpack. But, it's totally fine to use it as you are. It is published to the npm repository (that's why you were able to install it via yarn), but apparently even that was done by someone other than the author :).

[stof]

hmm, indeed, it is on npmjs.com, but their search feature looks shitty as giving the exact package name in the search field does not provide it in the quick results (though it is the first result when forcing to go to the result page).

Anyway, giving that Respond is only useful for IE 8 and older (all newer browsers support media queries), the fact that the library is not active anymore does not surprise me.

[weaverryan]

I've just added a FAQ about this: symfony/symfony-docs#8084

Cheers!