Error when using webpack in watch mode about enhanced-resolve

[daohoangson]

Looks like we have an undefined key here, likely from commit 03ef8f2:

		for(var key of this.data.keys()) {
			if(key.startsWith(what))
				this.data.delete(key);
		}

In a rush so I had to edit it like below as a temporary workaround:

		for(var key of this.data.keys()) {
			if (typeof key !== "string") {
				continue;
			}
			if(key.startsWith(what))
				this.data.delete(key);
		}

Hope this can be fixed soon.

[Alex-Sokolov]

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

[emaincourt]

Downgrading worked for me. If you're using Yarn, think about updating your yarn.lock file when you install 3.3.0 manually :

enhanced-resolve@^3.3.0:
  version "3.3.0"
  resolved "https://registry.yarnpkg.com/enhanced-resolve/-/enhanced-resolve-3.3.0.tgz#950964ecc7f0332a42321b673b38dc8ff15535b3"
  dependencies:
    graceful-fs "^4.1.2"
    memory-fs "^0.4.0"
    object-assign "^4.0.1"
    tapable "^0.2.5"

[smares]

Just wanted to report the same issue.

[peteringram0]

Also getting this issue.

[suyi91]

Getting the same problem using version 3.4.0

[antonnyman]

+1

[MadMikeyB]

+1

[Alvin-Liu]

+1

[timbergus]

Same error here.

webpack: Compiling...
/Users/Gustavo/Desktop/canvas-test/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:145

                    if(key.startsWith(what))
                          ^
TypeError: Cannot read property 'startsWith' of undefined

[the-architect]

Same issue, had to downgrade again.
Seems to work in 3.2.0.

[smares]

It even works in 3.3.0 @the-architect

[timobehrens]

+1

[code-by-gijs]

+1

[the-architect]

@smares yeah sorry, yarn was still installing 3.4.0.

[jeremyxgo]

Just facing the same error in 3.3.0
My script: cross-env NODE_ENV=development webpack-dev-server -d --inline --hot
When I edit my code and trigger the hot reload, the error shows and break the dev server

[bongofury]

+1

[Kumarsammy]

+1

[tomasztomys]

+1

[dariuszpaluch]

+1

[3jwddgm]

+1

[diegoprd]

+1

[danbruegge]

I tried downgrade to v3.3.0 and v3.2.0 with no success. I had to revert my upgrade from webpack-dev-server v2.6.1 back to v2.5.1. Now it is working again.

[antonnyman]

@daohoangson's fix works for me right now

[the-architect]

adding "enhanced-resolve": "3.3.0" to your package.json dependencies and running yarn is not enough? I can't try it out, because I deleted the yarn.lock file before.

[emaincourt]

@the-architect No since webpack expects "enhanced-resolve": "^3.3.0" so Yarn will resolve two different packages since patterns are different when you install it. You need to explicitly link them

[the-architect]

@emaincourt that's weird, but ok. thank you. :)

[danrot]

Works for me, thanks for fixing!

[danrot]

@tomasztomys Because of that comment: #97 (comment)

There is a new release which is fixing this issue.