Large number of errors when building with webpack
See original GitHub issueI get all these errors when I build with webpack:
ERROR in ./~/tough-cookie/package.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\tough-cookie\package.json Line 2: Unexpected toke
n :
You may need an appropriate loader to handle this file type.
| {
| "_args": [
| [
| "tough-cookie@~2.2.0",
@ ./~/tough-cookie/lib/cookie.js 38:14-40
ERROR in ./~/ms-rest/~/mime-db/db.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\ms-rest\node_modules\mime-db\db.json Line 2: Unex
pected token :
You may need an appropriate loader to handle this file type.
| {
| "application/1d-interleaved-parityfec": {
| "source": "iana"
| },
@ ./~/ms-rest/~/mime-db/index.js 11:17-37
ERROR in ./~/mime-db/db.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\mime-db\db.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
| "application/1d-interleaved-parityfec": {
| "source": "iana"
| },
@ ./~/mime-db/index.js 11:17-37
ERROR in ./~/har-validator/lib/schemas/cache.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\cache.json Line 2: Unex
pected token :
You may need an appropriate loader to handle this file type.
| {
| "properties": {
| "beforeRequest": {
| "$ref": "#cacheEntry"
@ ./~/har-validator/lib/schemas/index.js 4:9-32
ERROR in ./~/har-validator/lib/schemas/cacheEntry.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\cacheEntry.json Line 2:
Unexpected token :
You may need an appropriate loader to handle this file type.
| {
| "oneOf": [{
| "type": "object",
| "optional": true,
@ ./~/har-validator/lib/schemas/index.js 5:14-42
ERROR in ./~/har-validator/lib/schemas/content.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\content.json Line 2: Un
expected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "required": [
| "size",
@ ./~/har-validator/lib/schemas/index.js 6:11-36
ERROR in ./~/har-validator/lib/schemas/entry.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\entry.json Line 2: Unex
pected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "optional": true,
| "required": [
@ ./~/har-validator/lib/schemas/index.js 9:9-32
ERROR in ./~/har-validator/lib/schemas/cookie.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\cookie.json Line 2: Une
xpected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "required": [
| "name",
@ ./~/har-validator/lib/schemas/index.js 7:10-34
ERROR in ./~/har-validator/lib/schemas/page.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\page.json Line 2: Unexp
ected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "optional": true,
| "required": [
@ ./~/har-validator/lib/schemas/index.js 12:8-30
ERROR in ./~/har-validator/lib/schemas/creator.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\creator.json Line 2: Un
expected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "required": [
| "name",
@ ./~/har-validator/lib/schemas/index.js 8:11-36
ERROR in ./~/har-validator/lib/schemas/log.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\log.json Line 2: Unexpe
cted token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "required": [
| "version",
@ ./~/har-validator/lib/schemas/index.js 11:7-28
ERROR in ./~/har-validator/lib/schemas/pageTimings.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\pageTimings.json Line 2
: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "properties": {
| "onContentLoad": {
@ ./~/har-validator/lib/schemas/index.js 13:15-44
ERROR in ./~/har-validator/lib/schemas/postData.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\postData.json Line 2: U
nexpected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "optional": true,
| "required": [
@ ./~/har-validator/lib/schemas/index.js 14:12-38
ERROR in ./~/har-validator/lib/schemas/record.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\record.json Line 2: Une
xpected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "required": [
| "name",
@ ./~/har-validator/lib/schemas/index.js 15:10-34
ERROR in ./~/har-validator/lib/schemas/response.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\response.json Line 2: U
nexpected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "required": [
| "status",
@ ./~/har-validator/lib/schemas/index.js 17:12-38
ERROR in ./~/har-validator/lib/schemas/har.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\har.json Line 2: Unexpe
cted token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "required": [
| "log"
@ ./~/har-validator/lib/schemas/index.js 10:7-28
ERROR in ./~/har-validator/lib/schemas/request.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\request.json Line 2: Un
expected token :
You may need an appropriate loader to handle this file type.
| {
| "type": "object",
| "required": [
| "method",
@ ./~/har-validator/lib/schemas/index.js 16:11-36
ERROR in ./~/har-validator/lib/schemas/timings.json
Module parse failed: C:\Users\blah\devel\nextshot\node_modules\har-validator\lib\schemas\timings.json Line 2: Un
expected token :
You may need an appropriate loader to handle this file type.
| {
| "required": [
| "send",
| "wait",
@ ./~/har-validator/lib/schemas/index.js 18:11-36
Issue Analytics
- State:
- Created 8 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
How I solved and debugged my Webpack issue through trial ...
When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.
Read more >Build Performance - webpack
This guide contains some useful tips for improving build/compilation performance. ... Webpack 4 outputs a large amount of data with its stats.
Read more >Compile error with a lot of errors from webpack - Stack Overflow
I am receiving error, compiling graphql doesn't work because of the graphql-js dependency. Version: webpack 4.43.0 Time: 69237ms Built at: ...
Read more >Large number errors in webpack logs for update_from_* CI jobs
If you want to also speed up the build for test env. you can try disabling source maps (huge savings), excluding node_modules from...
Read more >This will make you more efficient at debugging Webpack ...
Webpack does its job and reports the error, but doesn't give you any clue as to where exactly this error comes from. Debugging...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m doing node.js with webpack, not for web browser development but for electron desktop application development.
Webpack is an extremely common build tool - probably the primary build tool in use. It would be a real problem if it isn’t supported.
If you are willing to try to get it to work with webpack that would be much appreciated because without webpack support our Azure support cannot be implemented.
We are coming up with a new repo altogether that will have isomorphic javascript sdks with crisp typescript type definitions. They will work in the browser and in node.js environment.