How to fix Missing Origin Validation error for “webpack-dev-server” in npm
up vote
4
down vote
favorite
npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.6
Dependency of laravel-mix [dev]
Path laravel-mix > webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 11710 scanned packages
1 vulnerability requires manual review. See the full report for details.
How to fix this i cannot use laravel
whenever i try run command "npm run dev" it shows several problem
laravel-5 npm laravel-5.2
asked Nov 11 at 3:29
Subhankar Jana
265
add a comment |
up vote
4
down vote
favorite
npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.6
Dependency of laravel-mix [dev]
Path laravel-mix > webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 11710 scanned packages
1 vulnerability requires manual review. See the full report for details.
How to fix this i cannot use laravel
whenever i try run command "npm run dev" it shows several problem
laravel-5 npm laravel-5.2
asked Nov 11 at 3:29
Subhankar Jana
265
add a comment |
up vote
4
down vote
favorite
up vote
4
down vote
favorite
npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.6
Dependency of laravel-mix [dev]
Path laravel-mix > webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 11710 scanned packages
1 vulnerability requires manual review. See the full report for details.
How to fix this i cannot use laravel
whenever i try run command "npm run dev" it shows several problem
laravel-5 npm laravel-5.2
asked Nov 11 at 3:29
Subhankar Jana
265
npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.6
Dependency of laravel-mix [dev]
Path laravel-mix > webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 11710 scanned packages
1 vulnerability requires manual review. See the full report for details.
How to fix this i cannot use laravel
whenever i try run command "npm run dev" it shows several problem
laravel-5 npm laravel-5.2
laravel-5 npm laravel-5.2
asked Nov 11 at 3:29
Subhankar Jana
265
asked Nov 11 at 3:29
Subhankar Jana
265
asked Nov 11 at 3:29
Subhankar Jana
265
asked Nov 11 at 3:29
Subhankar Jana
265
asked Nov 11 at 3:29
Subhankar Jana
265
265
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.
I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.
If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.
answered Nov 11 at 20:13
wheelmaker
1,209817
add a comment |
up vote
0
down vote
Quick solution:
Turning off npm audit on package installation
https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities
answered Nov 14 at 15:19
Julian
1
1
A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
– LazerBass
Nov 14 at 15:43
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.
I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.
If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.
answered Nov 11 at 20:13
wheelmaker
1,209817
add a comment |
up vote
3
down vote
This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.
I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.
If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.
answered Nov 11 at 20:13
wheelmaker
1,209817
add a comment |
up vote
3
down vote
up vote
3
down vote
This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.
I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.
If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.
answered Nov 11 at 20:13
wheelmaker
1,209817
This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.
I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.
If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.
answered Nov 11 at 20:13
wheelmaker
1,209817
edited Nov 19 at 2:24
answered Nov 11 at 20:13
wheelmaker
1,209817
answered Nov 11 at 20:13
wheelmaker
1,209817
answered Nov 11 at 20:13
wheelmaker
1,209817
1,209817
add a comment |
add a comment |
up vote
0
down vote
Quick solution:
Turning off npm audit on package installation
https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities
answered Nov 14 at 15:19
Julian
1
1
A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
– LazerBass
Nov 14 at 15:43
add a comment |
up vote
0
down vote
Quick solution:
Turning off npm audit on package installation
https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities
answered Nov 14 at 15:19
Julian
1
1
A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
– LazerBass
Nov 14 at 15:43
add a comment |
up vote
0
down vote
up vote
0
down vote
Quick solution:
Turning off npm audit on package installation
https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities
answered Nov 14 at 15:19
Julian
1
Quick solution:
Turning off npm audit on package installation
https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities
answered Nov 14 at 15:19
Julian
1
answered Nov 14 at 15:19
Julian
1
answered Nov 14 at 15:19
Julian
1
answered Nov 14 at 15:19
Julian
1
1
1
A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
– LazerBass
Nov 14 at 15:43
add a comment |
1
A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
– LazerBass
Nov 14 at 15:43
1
1
A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
– LazerBass
Nov 14 at 15:43
A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
– LazerBass
Nov 14 at 15:43
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53245592%2fhow-to-fix-missing-origin-validation-error-for-webpack-dev-server-in-npm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
