Expo DevTools TypeError: Cannot read property 'compile' of undefined
I cannot get the Expo DevTools to work.
My approach:
npm install -g expo-cli
expo init
cd PROJECTNAME
expo start
I just get this error message in the console:
TypeError: Cannot read property 'compile' of undefined
And this one in the DevTools in the browser:
Expo Developer Tools is disconnected from Expo CLI. Use the expo start
command to start the CLI again.
Does anyone know what Iam missing here?
react-native expo
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
asked Nov 25 '18 at 21:15
FBaFBa
755
add a comment |
I cannot get the Expo DevTools to work.
My approach:
npm install -g expo-cli
expo init
cd PROJECTNAME
expo start
I just get this error message in the console:
TypeError: Cannot read property 'compile' of undefined
And this one in the DevTools in the browser:
Expo Developer Tools is disconnected from Expo CLI. Use the expo start
command to start the CLI again.
Does anyone know what Iam missing here?
react-native expo
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
asked Nov 25 '18 at 21:15
FBaFBa
755
1
I started getting this error today after upgrading expo-cli from 2.1.0 to latest. Reverting to 2.1.0 did not fix the error.
– Skyler Austin
Nov 25 '18 at 21:33
I'm getting the same error when running expo start.
– TariqN
Nov 25 '18 at 21:50
I also got this error just now, I have two VMs in one of the VMs its working fine. To be further sure I made a new project by doing 'expo init' then expo start and it crashes for the new project as well.
– Lenny Linus
Nov 25 '18 at 21:50
5
Just filed a github issue with all the details: github.com/expo/expo-cli/issues/213
– Lenny Linus
Nov 25 '18 at 22:08
add a comment |
I cannot get the Expo DevTools to work.
My approach:
npm install -g expo-cli
expo init
cd PROJECTNAME
expo start
I just get this error message in the console:
TypeError: Cannot read property 'compile' of undefined
And this one in the DevTools in the browser:
Expo Developer Tools is disconnected from Expo CLI. Use the expo start
command to start the CLI again.
Does anyone know what Iam missing here?
react-native expo
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
asked Nov 25 '18 at 21:15
FBaFBa
755
I cannot get the Expo DevTools to work.
My approach:
npm install -g expo-cli
expo init
cd PROJECTNAME
expo start
I just get this error message in the console:
TypeError: Cannot read property 'compile' of undefined
And this one in the DevTools in the browser:
Expo Developer Tools is disconnected from Expo CLI. Use the expo start
command to start the CLI again.
Does anyone know what Iam missing here?
react-native expo
react-native expo
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
asked Nov 25 '18 at 21:15
FBaFBa
755
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
asked Nov 25 '18 at 21:15
FBaFBa
755
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
60.3k1477121
asked Nov 25 '18 at 21:15
FBaFBa
755
asked Nov 25 '18 at 21:15
FBaFBa
755
asked Nov 25 '18 at 21:15
FBaFBa
755
755
1
I started getting this error today after upgrading expo-cli from 2.1.0 to latest. Reverting to 2.1.0 did not fix the error.
– Skyler Austin
Nov 25 '18 at 21:33
I'm getting the same error when running expo start.
– TariqN
Nov 25 '18 at 21:50
I also got this error just now, I have two VMs in one of the VMs its working fine. To be further sure I made a new project by doing 'expo init' then expo start and it crashes for the new project as well.
– Lenny Linus
Nov 25 '18 at 21:50
5
Just filed a github issue with all the details: github.com/expo/expo-cli/issues/213
– Lenny Linus
Nov 25 '18 at 22:08
add a comment |
1
I started getting this error today after upgrading expo-cli from 2.1.0 to latest. Reverting to 2.1.0 did not fix the error.
– Skyler Austin
Nov 25 '18 at 21:33
I'm getting the same error when running expo start.
– TariqN
Nov 25 '18 at 21:50
I also got this error just now, I have two VMs in one of the VMs its working fine. To be further sure I made a new project by doing 'expo init' then expo start and it crashes for the new project as well.
– Lenny Linus
Nov 25 '18 at 21:50
5
Just filed a github issue with all the details: github.com/expo/expo-cli/issues/213
– Lenny Linus
Nov 25 '18 at 22:08
1
1
I started getting this error today after upgrading expo-cli from 2.1.0 to latest. Reverting to 2.1.0 did not fix the error.
– Skyler Austin
Nov 25 '18 at 21:33
I started getting this error today after upgrading expo-cli from 2.1.0 to latest. Reverting to 2.1.0 did not fix the error.
– Skyler Austin
Nov 25 '18 at 21:33
I'm getting the same error when running expo start.
– TariqN
Nov 25 '18 at 21:50
I'm getting the same error when running expo start.
– TariqN
Nov 25 '18 at 21:50
I also got this error just now, I have two VMs in one of the VMs its working fine. To be further sure I made a new project by doing 'expo init' then expo start and it crashes for the new project as well.
– Lenny Linus
Nov 25 '18 at 21:50
I also got this error just now, I have two VMs in one of the VMs its working fine. To be further sure I made a new project by doing 'expo init' then expo start and it crashes for the new project as well.
– Lenny Linus
Nov 25 '18 at 21:50
5
5
Just filed a github issue with all the details: github.com/expo/expo-cli/issues/213
– Lenny Linus
Nov 25 '18 at 22:08
Just filed a github issue with all the details: github.com/expo/expo-cli/issues/213
– Lenny Linus
Nov 25 '18 at 22:08
add a comment |
3 Answers
3
active
oldest
votes
This issue has now been solved. They just published expo-cli@2.4.1 and uninstalling and reinstalling makes it work:
npm uninstall -g expo-cli && npm i -g expo-cli
The issue was with a dependency of expo-cli 'joi' that was updated and broke stuff.
For more info: https://github.com/expo/expo-cli/issues/213
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
answered Nov 26 '18 at 9:53
Lenny LinusLenny Linus
36829
add a comment |
You aren't missing anything here - there appears to be a problem with this version of expo-cli.
The github thread shared in the comments has more information and a possible workaround. https://github.com/expo/expo-cli/issues/213
If the workaround doesn't work for you, I would suggest using react-native-cli or simply waiting a day or two until the expo team fix this issue.
answered Nov 26 '18 at 8:03
jmknolljmknoll
592523
add a comment |
I've managed to fix this issue changing the ExpoCli version.
Looking good with expo-cli 2.2.5. You can use it until they fix the issue with the latest version.
- Uninstall expo-cli
npm install -g expo-cli@2.2.5
After starting project all looks good.
There is a new version of expo-cli available (2.4.0).
You are currently using expo-cli 2.2.5
Run `npm install -g expo-cli` to get the latest version
answered Nov 26 '18 at 14:55
TariqNTariqN
1471215
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%2f53472046%2fexpo-devtools-typeerror-cannot-read-property-compile-of-undefined%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This issue has now been solved. They just published expo-cli@2.4.1 and uninstalling and reinstalling makes it work:
npm uninstall -g expo-cli && npm i -g expo-cli
The issue was with a dependency of expo-cli 'joi' that was updated and broke stuff.
For more info: https://github.com/expo/expo-cli/issues/213
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
answered Nov 26 '18 at 9:53
Lenny LinusLenny Linus
36829
add a comment |
This issue has now been solved. They just published expo-cli@2.4.1 and uninstalling and reinstalling makes it work:
npm uninstall -g expo-cli && npm i -g expo-cli
The issue was with a dependency of expo-cli 'joi' that was updated and broke stuff.
For more info: https://github.com/expo/expo-cli/issues/213
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
answered Nov 26 '18 at 9:53
Lenny LinusLenny Linus
36829
add a comment |
This issue has now been solved. They just published expo-cli@2.4.1 and uninstalling and reinstalling makes it work:
npm uninstall -g expo-cli && npm i -g expo-cli
The issue was with a dependency of expo-cli 'joi' that was updated and broke stuff.
For more info: https://github.com/expo/expo-cli/issues/213
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
answered Nov 26 '18 at 9:53
Lenny LinusLenny Linus
36829
This issue has now been solved. They just published expo-cli@2.4.1 and uninstalling and reinstalling makes it work:
npm uninstall -g expo-cli && npm i -g expo-cli
The issue was with a dependency of expo-cli 'joi' that was updated and broke stuff.
For more info: https://github.com/expo/expo-cli/issues/213
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
answered Nov 26 '18 at 9:53
Lenny LinusLenny Linus
36829
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
edited Dec 2 '18 at 11:13
Mark Rotteveel
60.3k1477121
60.3k1477121
answered Nov 26 '18 at 9:53
Lenny LinusLenny Linus
36829
answered Nov 26 '18 at 9:53
Lenny LinusLenny Linus
36829
answered Nov 26 '18 at 9:53
Lenny LinusLenny Linus
36829
36829
add a comment |
add a comment |
You aren't missing anything here - there appears to be a problem with this version of expo-cli.
The github thread shared in the comments has more information and a possible workaround. https://github.com/expo/expo-cli/issues/213
If the workaround doesn't work for you, I would suggest using react-native-cli or simply waiting a day or two until the expo team fix this issue.
answered Nov 26 '18 at 8:03
jmknolljmknoll
592523
add a comment |
You aren't missing anything here - there appears to be a problem with this version of expo-cli.
The github thread shared in the comments has more information and a possible workaround. https://github.com/expo/expo-cli/issues/213
If the workaround doesn't work for you, I would suggest using react-native-cli or simply waiting a day or two until the expo team fix this issue.
answered Nov 26 '18 at 8:03
jmknolljmknoll
592523
add a comment |
You aren't missing anything here - there appears to be a problem with this version of expo-cli.
The github thread shared in the comments has more information and a possible workaround. https://github.com/expo/expo-cli/issues/213
If the workaround doesn't work for you, I would suggest using react-native-cli or simply waiting a day or two until the expo team fix this issue.
answered Nov 26 '18 at 8:03
jmknolljmknoll
592523
You aren't missing anything here - there appears to be a problem with this version of expo-cli.
The github thread shared in the comments has more information and a possible workaround. https://github.com/expo/expo-cli/issues/213
If the workaround doesn't work for you, I would suggest using react-native-cli or simply waiting a day or two until the expo team fix this issue.
answered Nov 26 '18 at 8:03
jmknolljmknoll
592523
answered Nov 26 '18 at 8:03
jmknolljmknoll
592523
answered Nov 26 '18 at 8:03
jmknolljmknoll
592523
answered Nov 26 '18 at 8:03
jmknolljmknoll
592523
592523
add a comment |
add a comment |
I've managed to fix this issue changing the ExpoCli version.
Looking good with expo-cli 2.2.5. You can use it until they fix the issue with the latest version.
- Uninstall expo-cli
npm install -g expo-cli@2.2.5
After starting project all looks good.
There is a new version of expo-cli available (2.4.0).
You are currently using expo-cli 2.2.5
Run `npm install -g expo-cli` to get the latest version
answered Nov 26 '18 at 14:55
TariqNTariqN
1471215
add a comment |
I've managed to fix this issue changing the ExpoCli version.
Looking good with expo-cli 2.2.5. You can use it until they fix the issue with the latest version.
- Uninstall expo-cli
npm install -g expo-cli@2.2.5
After starting project all looks good.
There is a new version of expo-cli available (2.4.0).
You are currently using expo-cli 2.2.5
Run `npm install -g expo-cli` to get the latest version
answered Nov 26 '18 at 14:55
TariqNTariqN
1471215
add a comment |
I've managed to fix this issue changing the ExpoCli version.
Looking good with expo-cli 2.2.5. You can use it until they fix the issue with the latest version.
- Uninstall expo-cli
npm install -g expo-cli@2.2.5
After starting project all looks good.
There is a new version of expo-cli available (2.4.0).
You are currently using expo-cli 2.2.5
Run `npm install -g expo-cli` to get the latest version
answered Nov 26 '18 at 14:55
TariqNTariqN
1471215
I've managed to fix this issue changing the ExpoCli version.
Looking good with expo-cli 2.2.5. You can use it until they fix the issue with the latest version.
- Uninstall expo-cli
npm install -g expo-cli@2.2.5
After starting project all looks good.
There is a new version of expo-cli available (2.4.0).
You are currently using expo-cli 2.2.5
Run `npm install -g expo-cli` to get the latest version
answered Nov 26 '18 at 14:55
TariqNTariqN
1471215
answered Nov 26 '18 at 14:55
TariqNTariqN
1471215
answered Nov 26 '18 at 14:55
TariqNTariqN
1471215
answered Nov 26 '18 at 14:55
TariqNTariqN
1471215
1471215
add a comment |
add a comment |
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%2f53472046%2fexpo-devtools-typeerror-cannot-read-property-compile-of-undefined%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
1
I started getting this error today after upgrading expo-cli from 2.1.0 to latest. Reverting to 2.1.0 did not fix the error.
– Skyler Austin
Nov 25 '18 at 21:33
I'm getting the same error when running expo start.
– TariqN
Nov 25 '18 at 21:50
I also got this error just now, I have two VMs in one of the VMs its working fine. To be further sure I made a new project by doing 'expo init' then expo start and it crashes for the new project as well.
– Lenny Linus
Nov 25 '18 at 21:50
5
Just filed a github issue with all the details: github.com/expo/expo-cli/issues/213
– Lenny Linus
Nov 25 '18 at 22:08