Never reaches following code every second time
See original GitHub issueHello you are free to close this issue if not enough information provided,
We are seeing this issue ~every second deploy
global.webpackIsomorphicTools = new WebpackIsomorphicTools(webpackIsomorphicAssets)
.development(!serverConfig.isProduction)
.server(rootDir, () => {
console.log('Reached here 2');
require('./main.js');
});
this console.log
always fires, but in main.js
at the very top of the file there is another console.log
which doesn’t fire every second time and our deployment fails due to timeout. Any idea why this might happen?
Issue Analytics
- State:
- Created 7 years ago
- Comments:19 (8 by maintainers)
Top Results From Across the Web
python - Run certain code every n seconds - Stack Overflow
So this doesn't fire precisely every n seconds; rather, it drifts, with a bit more than n seconds between jobs. A 1 second...
Read more >Scheduling: setTimeout and setInterval
That's called “scheduling a call”. There are two methods for it: setTimeout allows us to run a function once after the interval of...
Read more >Unemployment FAQs - Kansas Department Of Labor
When filing a new application, you will need the following information: ... Zip Code and PO Box if you use one; A phone...
Read more >JavaScript Timers with setTimeout and setInterval
In this tutorial we'll look at JavaScript's setTimeout(), clearTimeout(), setInterval() and clearInterval() methods, and show how to use ...
Read more >JavaScript Timers: Everything you need to know
Write a script to print the message “Hello World” every second, but only 5 times. After 5 times, the script should print the...
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 FreeTop 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
Top GitHub Comments
@brotzky Feel free to ask questions on
universal-webpack
in a new thread in that repo. It’s not that hard to set up. Consult the example project for reference.Thanks!
I think I’ll try moving our code base over to
universal-webpack
. I’ve usedwebpack-isomorphic-tools
before and it wasn’t an issue, but that project didn’t useExtractTextPlugin
since it was purely Styled Components.Nextjs
doesn’t provide our project enough flexibility, but I have used it on small personal side projects and it has been great!