Skip to content

Getting errors on client build. #367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ddaza opened this issue Jan 11, 2016 · 22 comments
Closed

Getting errors on client build. #367

ddaza opened this issue Jan 11, 2016 · 22 comments

Comments

@ddaza
Copy link

ddaza commented Jan 11, 2016

Updated to webpack

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(/\/[^\/]+$/, "");
@EvHaus
Copy link

EvHaus commented Jan 11, 2016

+1 This issue was introduced with [email protected]. When I rollback to [email protected], everything is fine again

@minicuper
Copy link

+1
Guys, you can search the script element by id or something. No guarantee the last one is yours.

@cloudsan
Copy link

+1, rollback to @1.14.0 is fine for me,

@crestenstclair
Copy link

👍

@le0pard
Copy link

le0pard commented Jan 15, 2016

The same error after update to 1.4.1

@liujason
Copy link

+1 rolledback to @1.14.0 fixed the problem.

@jaylinski
Copy link

also getting this error on client when adding an inline-script-tag

+1 rolled back to @1.14.0 fixed the problem.

@Stas404
Copy link

Stas404 commented Feb 9, 2016

+1 hi all.

@kwtangerine
Copy link

+1. thanks for the tip, rolling back to 1.14.0 works for me too

@christophehurpeau
Copy link

👍

@kenjim83
Copy link

+1 me too. 1.14.0 works.

@Qrysto
Copy link

Qrysto commented Feb 15, 2016

+1, same issue as this and #381. Why is this unresolved for so long?

@goodseller
Copy link

+1

@jaylinski
Copy link

@sokra can you have a quick look at this? there are already two issues and three PRs open for this problem.
#381 #300 #394 #396 #447

@jakubzitny
Copy link

+1

3 similar comments
@denich
Copy link

denich commented Mar 19, 2016

+1

@foxtree
Copy link

foxtree commented Mar 28, 2016

+1

@incleaf
Copy link

incleaf commented Apr 10, 2016

+1

@numical
Copy link

numical commented Apr 13, 2016

+1

1 similar comment
@saponifi3d
Copy link

+1

@EvHaus
Copy link

EvHaus commented Jun 13, 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

@SpaceK33z
Copy link
Member

Dupe of #117.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests