Upgrading react-scripts on create-react-app results in a strange bug
I recently ran into the issue where an npm package I needed was not transpiled down to ES5 by the author. This meant that I needed to make sure that the conversion happened during my build stage. I did some research & found that upgrading from scripts 1.1.4 to 2.0.3 included what is needed to fix this. I ran the upgrade, cleared my yarn.lock file & deleted the node_modules folder. After this, I ran a yarn install again.
This led to everything working as expected. The build process runs all the way through & writes all files to the build folder. The app also works exactly as expected locally (i.e. before building). The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working. At first I thought that this was an issue with react-router, but then I tested by simply writing a console log message. This works locally before executing the build command, but after building the app, nothing happens on the click event. It does not throw an error neither does it write any info to the logs. I am quite stumped as I cannot seem to find anybody else that has run into this sort of behaviour before.
javascript reactjs yarnpkg
edited Nov 19 '18 at 17:13
tk421
3,40431426
asked Nov 19 '18 at 7:23
HermHerm
50511234
add a comment |
I recently ran into the issue where an npm package I needed was not transpiled down to ES5 by the author. This meant that I needed to make sure that the conversion happened during my build stage. I did some research & found that upgrading from scripts 1.1.4 to 2.0.3 included what is needed to fix this. I ran the upgrade, cleared my yarn.lock file & deleted the node_modules folder. After this, I ran a yarn install again.
This led to everything working as expected. The build process runs all the way through & writes all files to the build folder. The app also works exactly as expected locally (i.e. before building). The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working. At first I thought that this was an issue with react-router, but then I tested by simply writing a console log message. This works locally before executing the build command, but after building the app, nothing happens on the click event. It does not throw an error neither does it write any info to the logs. I am quite stumped as I cannot seem to find anybody else that has run into this sort of behaviour before.
javascript reactjs yarnpkg
edited Nov 19 '18 at 17:13
tk421
3,40431426
asked Nov 19 '18 at 7:23
HermHerm
50511234
The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working - regardless what the problem is, this behaviour is specific to your app. It's unlikely that it can be sorted out without investigating the problem. It's unclear whether the problem can be replicated locally but with built app,npm run buildinstead ofnpm run start. Could be mismatched React and ReactDOM versions or anything else.
– estus
Nov 19 '18 at 7:47
add a comment |
I recently ran into the issue where an npm package I needed was not transpiled down to ES5 by the author. This meant that I needed to make sure that the conversion happened during my build stage. I did some research & found that upgrading from scripts 1.1.4 to 2.0.3 included what is needed to fix this. I ran the upgrade, cleared my yarn.lock file & deleted the node_modules folder. After this, I ran a yarn install again.
This led to everything working as expected. The build process runs all the way through & writes all files to the build folder. The app also works exactly as expected locally (i.e. before building). The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working. At first I thought that this was an issue with react-router, but then I tested by simply writing a console log message. This works locally before executing the build command, but after building the app, nothing happens on the click event. It does not throw an error neither does it write any info to the logs. I am quite stumped as I cannot seem to find anybody else that has run into this sort of behaviour before.
javascript reactjs yarnpkg
edited Nov 19 '18 at 17:13
tk421
3,40431426
asked Nov 19 '18 at 7:23
HermHerm
50511234
I recently ran into the issue where an npm package I needed was not transpiled down to ES5 by the author. This meant that I needed to make sure that the conversion happened during my build stage. I did some research & found that upgrading from scripts 1.1.4 to 2.0.3 included what is needed to fix this. I ran the upgrade, cleared my yarn.lock file & deleted the node_modules folder. After this, I ran a yarn install again.
This led to everything working as expected. The build process runs all the way through & writes all files to the build folder. The app also works exactly as expected locally (i.e. before building). The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working. At first I thought that this was an issue with react-router, but then I tested by simply writing a console log message. This works locally before executing the build command, but after building the app, nothing happens on the click event. It does not throw an error neither does it write any info to the logs. I am quite stumped as I cannot seem to find anybody else that has run into this sort of behaviour before.
javascript reactjs yarnpkg
javascript reactjs yarnpkg
edited Nov 19 '18 at 17:13
tk421
3,40431426
asked Nov 19 '18 at 7:23
HermHerm
50511234
edited Nov 19 '18 at 17:13
tk421
3,40431426
asked Nov 19 '18 at 7:23
HermHerm
50511234
edited Nov 19 '18 at 17:13
tk421
3,40431426
edited Nov 19 '18 at 17:13
tk421
3,40431426
edited Nov 19 '18 at 17:13
tk421
3,40431426
3,40431426
asked Nov 19 '18 at 7:23
HermHerm
50511234
asked Nov 19 '18 at 7:23
HermHerm
50511234
asked Nov 19 '18 at 7:23
HermHerm
50511234
50511234
The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working - regardless what the problem is, this behaviour is specific to your app. It's unlikely that it can be sorted out without investigating the problem. It's unclear whether the problem can be replicated locally but with built app,npm run buildinstead ofnpm run start. Could be mismatched React and ReactDOM versions or anything else.
– estus
Nov 19 '18 at 7:47
add a comment |
The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working - regardless what the problem is, this behaviour is specific to your app. It's unlikely that it can be sorted out without investigating the problem. It's unclear whether the problem can be replicated locally but with built app,npm run buildinstead ofnpm run start. Could be mismatched React and ReactDOM versions or anything else.
– estus
Nov 19 '18 at 7:47
The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working - regardless what the problem is, this behaviour is specific to your app. It's unlikely that it can be sorted out without investigating the problem. It's unclear whether the problem can be replicated locally but with built app,
npm run build instead of npm run start. Could be mismatched React and ReactDOM versions or anything else.– estus
Nov 19 '18 at 7:47
The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working - regardless what the problem is, this behaviour is specific to your app. It's unlikely that it can be sorted out without investigating the problem. It's unclear whether the problem can be replicated locally but with built app,
npm run build instead of npm run start. Could be mismatched React and ReactDOM versions or anything else.– estus
Nov 19 '18 at 7:47
add a comment |
0
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',
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%2f53370006%2fupgrading-react-scripts-on-create-react-app-results-in-a-strange-bug%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53370006%2fupgrading-react-scripts-on-create-react-app-results-in-a-strange-bug%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
The weird behaviour however, is that after deploying the built application, none of my onClick events seem to be working - regardless what the problem is, this behaviour is specific to your app. It's unlikely that it can be sorted out without investigating the problem. It's unclear whether the problem can be replicated locally but with built app,
npm run buildinstead ofnpm run start. Could be mismatched React and ReactDOM versions or anything else.– estus
Nov 19 '18 at 7:47