Unable to run script after I run it through webpack. (Error: unable to locate global object)











up vote
1
down vote

favorite
1












I have a simple script.



script/src/index.js



var fetch = require('node-fetch');

console.log("working!")
...

exports = { createClient, createDevice };


script/webpack.config.js



const path = require('path');

module.exports = {
entry: './src/index.js',
mode: 'development',
output: {
filename: 'main.js',
path: path.resolve(__dirname, 'dist')
}
};


script/package.json



{
"name": "client",
"version": "1.0.0",
"private": true,
"dependencies": {
"node-fetch": "^2.3.0"
},
"devDependencies": {
"webpack": "^4.26.0",
"webpack-cli": "^3.1.2"
},
"scripts": {
"build": "webpack"
}
}


Running the source code works fine



node script/src/index.js
working!


Now I want to bundle the source code with the npm dependency so I run



npm run build


Then I try running the built code



node script/dist/main.js
webpack:///./node_modules/node-fetch/browser.js?:11
throw new Error('unable to locate global object');
^

Error: unable to locate global object
at getGlobal (webpack:///./node_modules/node-fetch/browser.js?:11:8)
at eval (webpack:///./node_modules/node-fetch/browser.js?:14:14)
at Object../node_modules/node-fetch/browser.js (/Users/xp025106/Dev/client-js/client/dist/main.js:97:1)
at __webpack_require__ (/Users/xp025106/Dev/client-js/client/dist/main.js:20:30)
at eval (webpack:///./src/index.js?:1:13)
at Object../src/index.js (/Users/xp025106/Dev/client-js/client/dist/main.js:108:1)
at __webpack_require__ (/Users/xp025106/Dev/client-js/client/dist/main.js:20:30)
at /Users/xp025106/Dev/client-js/client/dist/main.js:84:18
at Object.<anonymous> (/Users/xp025106/Dev/client-js/client/dist/main.js:87:10)
at Module._compile (module.js:652:30)


Why can I not run the built code the same way I could run the source code?










share|improve this question
























  • I think you want to run npm run build instead node run build, don't you?
    – Lucas Costa
    Nov 20 at 12:55












  • @LucasCosta: Fixed! Unfortunately that was just a typo in my question so the problem persists.
    – user1283776
    Nov 20 at 13:07






  • 1




    since the application target is node, use target: node. Otherwise it is going to focus on hitting the browser
    – PlayMa256
    Nov 20 at 13:10

















up vote
1
down vote

favorite
1












I have a simple script.



script/src/index.js



var fetch = require('node-fetch');

console.log("working!")
...

exports = { createClient, createDevice };


script/webpack.config.js



const path = require('path');

module.exports = {
entry: './src/index.js',
mode: 'development',
output: {
filename: 'main.js',
path: path.resolve(__dirname, 'dist')
}
};


script/package.json



{
"name": "client",
"version": "1.0.0",
"private": true,
"dependencies": {
"node-fetch": "^2.3.0"
},
"devDependencies": {
"webpack": "^4.26.0",
"webpack-cli": "^3.1.2"
},
"scripts": {
"build": "webpack"
}
}


Running the source code works fine



node script/src/index.js
working!


Now I want to bundle the source code with the npm dependency so I run



npm run build


Then I try running the built code



node script/dist/main.js
webpack:///./node_modules/node-fetch/browser.js?:11
throw new Error('unable to locate global object');
^

Error: unable to locate global object
at getGlobal (webpack:///./node_modules/node-fetch/browser.js?:11:8)
at eval (webpack:///./node_modules/node-fetch/browser.js?:14:14)
at Object../node_modules/node-fetch/browser.js (/Users/xp025106/Dev/client-js/client/dist/main.js:97:1)
at __webpack_require__ (/Users/xp025106/Dev/client-js/client/dist/main.js:20:30)
at eval (webpack:///./src/index.js?:1:13)
at Object../src/index.js (/Users/xp025106/Dev/client-js/client/dist/main.js:108:1)
at __webpack_require__ (/Users/xp025106/Dev/client-js/client/dist/main.js:20:30)
at /Users/xp025106/Dev/client-js/client/dist/main.js:84:18
at Object.<anonymous> (/Users/xp025106/Dev/client-js/client/dist/main.js:87:10)
at Module._compile (module.js:652:30)


Why can I not run the built code the same way I could run the source code?










share|improve this question
























  • I think you want to run npm run build instead node run build, don't you?
    – Lucas Costa
    Nov 20 at 12:55












  • @LucasCosta: Fixed! Unfortunately that was just a typo in my question so the problem persists.
    – user1283776
    Nov 20 at 13:07






  • 1




    since the application target is node, use target: node. Otherwise it is going to focus on hitting the browser
    – PlayMa256
    Nov 20 at 13:10















up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





I have a simple script.



script/src/index.js



var fetch = require('node-fetch');

console.log("working!")
...

exports = { createClient, createDevice };


script/webpack.config.js



const path = require('path');

module.exports = {
entry: './src/index.js',
mode: 'development',
output: {
filename: 'main.js',
path: path.resolve(__dirname, 'dist')
}
};


script/package.json



{
"name": "client",
"version": "1.0.0",
"private": true,
"dependencies": {
"node-fetch": "^2.3.0"
},
"devDependencies": {
"webpack": "^4.26.0",
"webpack-cli": "^3.1.2"
},
"scripts": {
"build": "webpack"
}
}


Running the source code works fine



node script/src/index.js
working!


Now I want to bundle the source code with the npm dependency so I run



npm run build


Then I try running the built code



node script/dist/main.js
webpack:///./node_modules/node-fetch/browser.js?:11
throw new Error('unable to locate global object');
^

Error: unable to locate global object
at getGlobal (webpack:///./node_modules/node-fetch/browser.js?:11:8)
at eval (webpack:///./node_modules/node-fetch/browser.js?:14:14)
at Object../node_modules/node-fetch/browser.js (/Users/xp025106/Dev/client-js/client/dist/main.js:97:1)
at __webpack_require__ (/Users/xp025106/Dev/client-js/client/dist/main.js:20:30)
at eval (webpack:///./src/index.js?:1:13)
at Object../src/index.js (/Users/xp025106/Dev/client-js/client/dist/main.js:108:1)
at __webpack_require__ (/Users/xp025106/Dev/client-js/client/dist/main.js:20:30)
at /Users/xp025106/Dev/client-js/client/dist/main.js:84:18
at Object.<anonymous> (/Users/xp025106/Dev/client-js/client/dist/main.js:87:10)
at Module._compile (module.js:652:30)


Why can I not run the built code the same way I could run the source code?










share|improve this question















I have a simple script.



script/src/index.js



var fetch = require('node-fetch');

console.log("working!")
...

exports = { createClient, createDevice };


script/webpack.config.js



const path = require('path');

module.exports = {
entry: './src/index.js',
mode: 'development',
output: {
filename: 'main.js',
path: path.resolve(__dirname, 'dist')
}
};


script/package.json



{
"name": "client",
"version": "1.0.0",
"private": true,
"dependencies": {
"node-fetch": "^2.3.0"
},
"devDependencies": {
"webpack": "^4.26.0",
"webpack-cli": "^3.1.2"
},
"scripts": {
"build": "webpack"
}
}


Running the source code works fine



node script/src/index.js
working!


Now I want to bundle the source code with the npm dependency so I run



npm run build


Then I try running the built code



node script/dist/main.js
webpack:///./node_modules/node-fetch/browser.js?:11
throw new Error('unable to locate global object');
^

Error: unable to locate global object
at getGlobal (webpack:///./node_modules/node-fetch/browser.js?:11:8)
at eval (webpack:///./node_modules/node-fetch/browser.js?:14:14)
at Object../node_modules/node-fetch/browser.js (/Users/xp025106/Dev/client-js/client/dist/main.js:97:1)
at __webpack_require__ (/Users/xp025106/Dev/client-js/client/dist/main.js:20:30)
at eval (webpack:///./src/index.js?:1:13)
at Object../src/index.js (/Users/xp025106/Dev/client-js/client/dist/main.js:108:1)
at __webpack_require__ (/Users/xp025106/Dev/client-js/client/dist/main.js:20:30)
at /Users/xp025106/Dev/client-js/client/dist/main.js:84:18
at Object.<anonymous> (/Users/xp025106/Dev/client-js/client/dist/main.js:87:10)
at Module._compile (module.js:652:30)


Why can I not run the built code the same way I could run the source code?







node.js webpack






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 at 13:06

























asked Nov 20 at 12:49









user1283776

3,1222154105




3,1222154105












  • I think you want to run npm run build instead node run build, don't you?
    – Lucas Costa
    Nov 20 at 12:55












  • @LucasCosta: Fixed! Unfortunately that was just a typo in my question so the problem persists.
    – user1283776
    Nov 20 at 13:07






  • 1




    since the application target is node, use target: node. Otherwise it is going to focus on hitting the browser
    – PlayMa256
    Nov 20 at 13:10




















  • I think you want to run npm run build instead node run build, don't you?
    – Lucas Costa
    Nov 20 at 12:55












  • @LucasCosta: Fixed! Unfortunately that was just a typo in my question so the problem persists.
    – user1283776
    Nov 20 at 13:07






  • 1




    since the application target is node, use target: node. Otherwise it is going to focus on hitting the browser
    – PlayMa256
    Nov 20 at 13:10


















I think you want to run npm run build instead node run build, don't you?
– Lucas Costa
Nov 20 at 12:55






I think you want to run npm run build instead node run build, don't you?
– Lucas Costa
Nov 20 at 12:55














@LucasCosta: Fixed! Unfortunately that was just a typo in my question so the problem persists.
– user1283776
Nov 20 at 13:07




@LucasCosta: Fixed! Unfortunately that was just a typo in my question so the problem persists.
– user1283776
Nov 20 at 13:07




1




1




since the application target is node, use target: node. Otherwise it is going to focus on hitting the browser
– PlayMa256
Nov 20 at 13:10






since the application target is node, use target: node. Otherwise it is going to focus on hitting the browser
– PlayMa256
Nov 20 at 13:10



















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53393363%2funable-to-run-script-after-i-run-it-through-webpack-error-unable-to-locate-gl%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53393363%2funable-to-run-script-after-i-run-it-through-webpack-error-unable-to-locate-gl%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Tonle Sap (See)

I get strange results when I access the Sqlitedatabase with Unity C# via XAMPP

Guatemaltekische Davis-Cup-Mannschaft