Webpack-dev-server: v2.6.1 CachedInputFileSystem error

Created on 24 Jul 2017 · 16Comments · Source: webpack/webpack-dev-server

if watch is enabled in webpack config:

/Users/burak.demirezen/Documents/Projects/widget-v3-configurator/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:145
            if(key.startsWith(what))
                  ^

TypeError: Cannot read property 'startsWith' of undefined
    at Storage.purge (/Users/burak.demirezen/Documents/Projects/widget-v3-configurator/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:145:10)
    at Storage.purge (/Users/burak.demirezen/Documents/Projects/widget-v3-configurator/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:150:9)
    at CachedInputFileSystem.purge (/Users/burak.demirezen/Documents/Projects/widget-v3-configurator/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:259:20)
    at EventEmitter.watcher.once (/Users/burak.demirezen/Documents/Projects/widget-v3-configurator/node_modules/webpack/lib/node/NodeWatchFileSystem.js:42:26)
    at EventEmitter.g (events.js:291:16)
    at emitTwo (events.js:106:13)
    at EventEmitter.emit (events.js:191:7)
    at EventEmitter._onTimeout (/Users/burak.demirezen/Documents/Projects/widget-v3-configurator/node_modules/watchpack/lib/watchpack.js:142:7)
    at ontimeout (timers.js:365:14)
    at tryOnTimeout (timers.js:237:5)
    at Timer.listOnTimeout (timers.js:207:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] deploy-dev: `webpack --config webpack-dev.config.js --colors --progress --profile`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] deploy-dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/burak.demirezen/.npm/_logs/2017-07-24T08_53_53_623Z-debug.log

Source

webyonet

👍1

Most helpful comment

Fixed in https://github.com/webpack/enhanced-resolve/releases/tag/v3.4.1

Alex-Sokolov on 24 Jul 2017

👍6

All 16 comments

sory this problem is only in the webpack v3.3.0

webyonet on 24 Jul 2017

@webyonet how you solve it?

Alex-Sokolov on 24 Jul 2017

Why this issue closed? I have similar error, with v3.3.0

AleshaOleg on 24 Jul 2017

@Alex-Sokolov you mentioned before, that it works with 2.5.1 for you. Is it true? If yes, could you show me your webpack config?

AleshaOleg on 24 Jul 2017

@AleshaOleg No, crashed also. Builded ok, but when hot reload start will crash

Alex-Sokolov on 24 Jul 2017

@Alex-Sokolov, same. Do you know, on which versions it will run now? I tried [email protected] now, it also crashed

AleshaOleg on 24 Jul 2017

Yea, this issue has been closed too soon. Experiencing the same result here.

coockoo on 24 Jul 2017

Here is solution: https://github.com/webpack/enhanced-resolve/issues/97

AleshaOleg on 24 Jul 2017

👍4

@AleshaOleg I have not solved the problem. WebPack has already opened issue for the same problem

webyonet on 24 Jul 2017

@webyonet you need downgrade enhanced-resolve to 3.3.0, not webpack or webpack-dev-server.

AleshaOleg on 24 Jul 2017

@AleshaOleg ok. thanks for helping

webyonet on 24 Jul 2017

Maybe someone knows how to downgrade enhanced-resolve to 3.3.0 with yarn (Assuming there is no dependency of enhanced-resolve in project, only webpack)

coockoo on 24 Jul 2017

@AleshaOleg @coockoo the problem was solved in enhanced-resolve 3.3.0

webyonet on 24 Jul 2017

Fixed in https://github.com/webpack/enhanced-resolve/releases/tag/v3.4.1

Alex-Sokolov on 24 Jul 2017

👍6

Can confirm, upgrade to 3.4.1 works.