“Cannot read property 'upgrade' of undefined” when starting vue applicationcannot read property 'apply' of undefined gulpwebpack-dev-server command not foundCannot `gulp install`, results in `Cannot read property 'apply' of undefined`Cannot Import ES6 module into Vue single file componentHow to make my VueCLI webpack-simple accessible in LAN (192.168.1.73:8080)?Build Vue+Vuetify use 'npm start build'cannot read property 'createResolver' of undefinedError on running npm run devHow to fix “This relative module was not found: * ./src/main.js in multi…” error when trying to npm run serve
How can one write good dialogue in a story without sounding wooden?
How did the hit man miss?
How to tell someone I'd like to become friends without letting them think I'm romantically interested in them?
How many hours would it take to watch all of Doctor Who?
Single word for "refusing to move to next activity unless present one is completed."
How can I calculate the sum of 2 random dice out of a 3d6 pool in AnyDice?
How to loop for 3 times in bash script when docker push fails?
Would dual wielding daggers be a viable choice for a covert bodyguard?
What is a solution?
What explains 9 speed cassettes price differences?
Credit score and financing new car
If your plane is out-of-control, why does military training instruct releasing the joystick to neutralize controls?
C program to parse source code of another language
Is the genetic term "polycistronic" still used in modern biology?
How to convert a file with several spaces into a tab-delimited file?
Why did Harry Potter get a bedroom?
Why isn't there research to build a standard lunar, or Martian mobility platform?
Cops: The Hidden OEIS Substring
Referring to different instances of the same character in time travel
Matchmaker, Matchmaker, make me a match
Should disabled buttons give feedback when clicked?
Why is a Gelman-Rubin diagnostic of < 1.1 considered acceptable?
Does Lufthansa weigh your carry on luggage?
Do you know your 'KVZ's?
“Cannot read property 'upgrade' of undefined” when starting vue application
cannot read property 'apply' of undefined gulpwebpack-dev-server command not foundCannot `gulp install`, results in `Cannot read property 'apply' of undefined`Cannot Import ES6 module into Vue single file componentHow to make my VueCLI webpack-simple accessible in LAN (192.168.1.73:8080)?Build Vue+Vuetify use 'npm start build'cannot read property 'createResolver' of undefinedError on running npm run devHow to fix “This relative module was not found: * ./src/main.js in multi…” error when trying to npm run serve
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have a project that's been running perfectly for a few months now, able to run npm run serve with no problem. I have to terminate and run the command again whenever I switch networks, but that has never been a problem and the server could always start again.
Until now - no matter what I do I can't get the server to start. I get this error:
npm run serve
> xbs@0.6.2 serve D:workspace[PROJECT]
> vue-cli-service serve
INFO Starting development server...
10% building 1/1 modules 0 active ERROR TypeError: Cannot read property 'upgrade' of undefined
TypeError: Cannot read property 'upgrade' of undefined
at Server.<anonymous> (D:workspace[PROJECT]node_moduleswebpack-dev-serverlibServer.js:667:47)
at Array.forEach (<anonymous>)
at new Server (D:workspace[PROJECT]node_moduleswebpack-dev-serverlibServer.js:666:22)
at serve (D:workspace[PROJECT]node_modules@vuecli-servicelibcommandsserve.js:137:20)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
The last time I got this message was when I forgot to set the .env files, but this is a previously working copy with all necessary files set, and no changes since the last working run.
I've even tried pulling a fresh copy of the repo, running npm i and setting all env files but it still fails.
npm run lint and npm run build can still work, only npm run serve.
Am I missing anything?
vue.js npm vuejs2 webpack-dev-server vue-cli-3
asked Mar 26 at 2:26
kkontagionkkontagion
666 bronze badges
add a comment |
I have a project that's been running perfectly for a few months now, able to run npm run serve with no problem. I have to terminate and run the command again whenever I switch networks, but that has never been a problem and the server could always start again.
Until now - no matter what I do I can't get the server to start. I get this error:
npm run serve
> xbs@0.6.2 serve D:workspace[PROJECT]
> vue-cli-service serve
INFO Starting development server...
10% building 1/1 modules 0 active ERROR TypeError: Cannot read property 'upgrade' of undefined
TypeError: Cannot read property 'upgrade' of undefined
at Server.<anonymous> (D:workspace[PROJECT]node_moduleswebpack-dev-serverlibServer.js:667:47)
at Array.forEach (<anonymous>)
at new Server (D:workspace[PROJECT]node_moduleswebpack-dev-serverlibServer.js:666:22)
at serve (D:workspace[PROJECT]node_modules@vuecli-servicelibcommandsserve.js:137:20)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
The last time I got this message was when I forgot to set the .env files, but this is a previously working copy with all necessary files set, and no changes since the last working run.
I've even tried pulling a fresh copy of the repo, running npm i and setting all env files but it still fails.
npm run lint and npm run build can still work, only npm run serve.
Am I missing anything?
vue.js npm vuejs2 webpack-dev-server vue-cli-3
asked Mar 26 at 2:26
kkontagionkkontagion
666 bronze badges
That line seems related to websocket proxies
– Phil
Mar 26 at 3:51
@Phil I'm lost - what do I do to fix it?
– kkontagion
Mar 26 at 3:54
What's in yourvue.config.jsfile?
– Phil
Mar 26 at 4:41
@Phil thanks for the hints -devServer.proxyin my vue config was indeed trying to access a no longer existent env variable. Oddly enough this wasn't a problem for the past week or so since I removed that variable, but removing the reference to the variable solved the problem. Thanks!
– kkontagion
Mar 26 at 6:07
add a comment |
I have a project that's been running perfectly for a few months now, able to run npm run serve with no problem. I have to terminate and run the command again whenever I switch networks, but that has never been a problem and the server could always start again.
Until now - no matter what I do I can't get the server to start. I get this error:
npm run serve
> xbs@0.6.2 serve D:workspace[PROJECT]
> vue-cli-service serve
INFO Starting development server...
10% building 1/1 modules 0 active ERROR TypeError: Cannot read property 'upgrade' of undefined
TypeError: Cannot read property 'upgrade' of undefined
at Server.<anonymous> (D:workspace[PROJECT]node_moduleswebpack-dev-serverlibServer.js:667:47)
at Array.forEach (<anonymous>)
at new Server (D:workspace[PROJECT]node_moduleswebpack-dev-serverlibServer.js:666:22)
at serve (D:workspace[PROJECT]node_modules@vuecli-servicelibcommandsserve.js:137:20)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
The last time I got this message was when I forgot to set the .env files, but this is a previously working copy with all necessary files set, and no changes since the last working run.
I've even tried pulling a fresh copy of the repo, running npm i and setting all env files but it still fails.
npm run lint and npm run build can still work, only npm run serve.
Am I missing anything?
vue.js npm vuejs2 webpack-dev-server vue-cli-3
asked Mar 26 at 2:26
kkontagionkkontagion
666 bronze badges
I have a project that's been running perfectly for a few months now, able to run npm run serve with no problem. I have to terminate and run the command again whenever I switch networks, but that has never been a problem and the server could always start again.
Until now - no matter what I do I can't get the server to start. I get this error:
npm run serve
> xbs@0.6.2 serve D:workspace[PROJECT]
> vue-cli-service serve
INFO Starting development server...
10% building 1/1 modules 0 active ERROR TypeError: Cannot read property 'upgrade' of undefined
TypeError: Cannot read property 'upgrade' of undefined
at Server.<anonymous> (D:workspace[PROJECT]node_moduleswebpack-dev-serverlibServer.js:667:47)
at Array.forEach (<anonymous>)
at new Server (D:workspace[PROJECT]node_moduleswebpack-dev-serverlibServer.js:666:22)
at serve (D:workspace[PROJECT]node_modules@vuecli-servicelibcommandsserve.js:137:20)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
The last time I got this message was when I forgot to set the .env files, but this is a previously working copy with all necessary files set, and no changes since the last working run.
I've even tried pulling a fresh copy of the repo, running npm i and setting all env files but it still fails.
npm run lint and npm run build can still work, only npm run serve.
Am I missing anything?
vue.js npm vuejs2 webpack-dev-server vue-cli-3
vue.js npm vuejs2 webpack-dev-server vue-cli-3
asked Mar 26 at 2:26
kkontagionkkontagion
666 bronze badges
asked Mar 26 at 2:26
kkontagionkkontagion
666 bronze badges
edited Mar 26 at 3:41
kkontagion
asked Mar 26 at 2:26
kkontagionkkontagion
666 bronze badges
asked Mar 26 at 2:26
kkontagionkkontagion
666 bronze badges
asked Mar 26 at 2:26
kkontagionkkontagion
666 bronze badges
666 bronze badges
That line seems related to websocket proxies
– Phil
Mar 26 at 3:51
@Phil I'm lost - what do I do to fix it?
– kkontagion
Mar 26 at 3:54
What's in yourvue.config.jsfile?
– Phil
Mar 26 at 4:41
@Phil thanks for the hints -devServer.proxyin my vue config was indeed trying to access a no longer existent env variable. Oddly enough this wasn't a problem for the past week or so since I removed that variable, but removing the reference to the variable solved the problem. Thanks!
– kkontagion
Mar 26 at 6:07
add a comment |
That line seems related to websocket proxies
– Phil
Mar 26 at 3:51
@Phil I'm lost - what do I do to fix it?
– kkontagion
Mar 26 at 3:54
What's in yourvue.config.jsfile?
– Phil
Mar 26 at 4:41
@Phil thanks for the hints -devServer.proxyin my vue config was indeed trying to access a no longer existent env variable. Oddly enough this wasn't a problem for the past week or so since I removed that variable, but removing the reference to the variable solved the problem. Thanks!
– kkontagion
Mar 26 at 6:07
That line seems related to websocket proxies
– Phil
Mar 26 at 3:51
That line seems related to websocket proxies
– Phil
Mar 26 at 3:51
@Phil I'm lost - what do I do to fix it?
– kkontagion
Mar 26 at 3:54
@Phil I'm lost - what do I do to fix it?
– kkontagion
Mar 26 at 3:54
What's in your
vue.config.js file?– Phil
Mar 26 at 4:41
What's in your
vue.config.js file?– Phil
Mar 26 at 4:41
@Phil thanks for the hints -
devServer.proxy in my vue config was indeed trying to access a no longer existent env variable. Oddly enough this wasn't a problem for the past week or so since I removed that variable, but removing the reference to the variable solved the problem. Thanks!– kkontagion
Mar 26 at 6:07
@Phil thanks for the hints -
devServer.proxy in my vue config was indeed trying to access a no longer existent env variable. Oddly enough this wasn't a problem for the past week or so since I removed that variable, but removing the reference to the variable solved the problem. Thanks!– kkontagion
Mar 26 at 6:07
add a comment |
1 Answer
1
active
oldest
votes
The problem was again with the .env files. My vue.config.js was trying to access a previously set environment variable that had since been removed.
Only strange thing was that there weren't any problems up til now?
answered Mar 26 at 6:04
kkontagionkkontagion
666 bronze badges
add a comment |
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',
autoActivateHeartbeat: false,
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
);
);
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%2f55348996%2fcannot-read-property-upgrade-of-undefined-when-starting-vue-application%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem was again with the .env files. My vue.config.js was trying to access a previously set environment variable that had since been removed.
Only strange thing was that there weren't any problems up til now?
answered Mar 26 at 6:04
kkontagionkkontagion
666 bronze badges
add a comment |
The problem was again with the .env files. My vue.config.js was trying to access a previously set environment variable that had since been removed.
Only strange thing was that there weren't any problems up til now?
answered Mar 26 at 6:04
kkontagionkkontagion
666 bronze badges
add a comment |
The problem was again with the .env files. My vue.config.js was trying to access a previously set environment variable that had since been removed.
Only strange thing was that there weren't any problems up til now?
answered Mar 26 at 6:04
kkontagionkkontagion
666 bronze badges
The problem was again with the .env files. My vue.config.js was trying to access a previously set environment variable that had since been removed.
Only strange thing was that there weren't any problems up til now?
answered Mar 26 at 6:04
kkontagionkkontagion
666 bronze badges
answered Mar 26 at 6:04
kkontagionkkontagion
666 bronze badges
answered Mar 26 at 6:04
kkontagionkkontagion
666 bronze badges
answered Mar 26 at 6:04
kkontagionkkontagion
666 bronze badges
666 bronze badges
add a comment |
add a comment |
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
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.
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%2f55348996%2fcannot-read-property-upgrade-of-undefined-when-starting-vue-application%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
That line seems related to websocket proxies
– Phil
Mar 26 at 3:51
@Phil I'm lost - what do I do to fix it?
– kkontagion
Mar 26 at 3:54
What's in your
vue.config.jsfile?– Phil
Mar 26 at 4:41
@Phil thanks for the hints -
devServer.proxyin my vue config was indeed trying to access a no longer existent env variable. Oddly enough this wasn't a problem for the past week or so since I removed that variable, but removing the reference to the variable solved the problem. Thanks!– kkontagion
Mar 26 at 6:07