Webpack-dev-server: Getting errors on client build.
Updated to webpack
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
I am seeing an error:
Uncaught TypeError: Cannot read property 'replace' of null
in line 5 of webpack-dev-server/client/index.js :
var scriptHost = scriptElements[scriptElements.length-1].getAttribute("src").replace(/\/[^\/]+$/, "");
ddaza
All 22 comments
+1 This issue was introduced with [email protected]. When I rollback to [email protected], everything is fine again
EvHaus
on 12 Jan 2016
+1
Guys, you can search the script element by id or something. No guarantee the last one is yours.
minicuper
on 12 Jan 2016
+1, rollback to @1.14.0 is fine for me,
cloudsan
on 12 Jan 2016
:+1:
crestenstclair
on 12 Jan 2016
The same error after update to 1.4.1
le0pard
on 15 Jan 2016
+1 rolledback to @1.14.0 fixed the problem.
liujason
on 21 Jan 2016
also getting this error on client when adding an inline-script-tag
+1 rolled back to @1.14.0 fixed the problem.
jaylinski
on 22 Jan 2016
+1 hi all.
Stas404
on 9 Feb 2016
+1. thanks for the tip, rolling back to 1.14.0 works for me too
kwtangerine
on 10 Feb 2016
:+1:
christophehurpeau
on 12 Feb 2016
+1 me too. 1.14.0 works.
kenjim83
on 12 Feb 2016
+1, same issue as this and #381. Why is this unresolved for so long?
Qrysto
on 15 Feb 2016
+1
goodseller
on 16 Feb 2016
@sokra can you have a quick look at this? there are already two issues and three PRs open for this problem.
https://github.com/webpack/webpack-dev-server/issues/381 https://github.com/webpack/webpack-dev-server/pull/300 https://github.com/webpack/webpack-dev-server/pull/394 https://github.com/webpack/webpack-dev-server/pull/396 https://github.com/webpack/webpack-dev-server/pull/447
jaylinski
on 18 Feb 2016
+1
jakubzitny
on 4 Mar 2016
+1
denich
on 19 Mar 2016
+1
foxtree
on 28 Mar 2016
+1
incleaf
on 10 Apr 2016
+1
numical
on 13 Apr 2016
+1
saponifi3d
on 29 Apr 2016
For those who want to make the leap to Webpack 2.0 beta, this issue appears to be fixed in webpack-dev-server 2.1.0-beta.0
EvHaus
on 13 Jun 2016
Dupe of #117.
SpaceK33z
on 21 Aug 2016
Related issues
mrdulin
·
3Comments
gimmi
·
3Comments
piotrszaredko
·
3Comments
nikirossi
·
3Comments
subblue
·
3Comments
Most helpful comment
+1 This issue was introduced with [email protected]. When I rollback to [email protected], everything is fine again