Gatsby develop stuck on Windows 10 #25216
Comments
gatsbot
bot
added
the
status: triage needed
|
Hi @mimiza! Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a minimal reproduction. This is a simplified example of the issue that makes it clear and obvious what the issue is and how we can begin to debug it. If you're up for it, we'd very much appreciate if you could provide a minimal reproduction and we'll be able to take another look. Additionally, it would be helpful to know more about your environment (e.g. which terminal application you are using, which editor, etc.) in order to help locate the bug. Thanks for using Gatsby! 💜 |
madalynrose
added
status: needs more info
|
@madalynrose Hi there! |
wardpeet
added
topic: plugins-PWA
|
Hey @mimiza. I could reproduce this one but I don't really know the reason why this happens. Maybe it's the svg 🤷 @moonmeister do you know of any race conditions that can occur here? |
|
I'm not aware of anything off hand but possible. Maybe file system related too. If I get a chance I'll do some testing now that I have a windows machine. |
|
@wardpeet @moonmeister thank you for supporting. But if it was about svg, why would Linux work? |
This comment has been minimized.
This comment has been minimized.
|
I have exactly the same issue as @mimiza. |
|
SInce my initial testing I've been doing more windows dev and run into this issue as well. I'm not convinced the bug is in |
moonmeister
added
the
status: confirmed
|
I've also had this issue, but via |
|
This issue happened to me while I used default starter, removed |
My solution was;
|
|
This is happening to me now too. Repository. It started happening a little before my current commit, but I was able to get around it by running the command again so I kept working. My page seems to have gotten slower and to the point where the JS breaks with my most recent addition so I'm going to have to look in to if that is something I caused but I'm too tired to do that tonight. |
|
It seems the problem was my Node not being up to date. I was able to develop my site fine up until some point where this started happening. Updating Node fixed that issue. I fixed my other issue also. |
|
I have been dealing with this issue from day one of using Gatsby. No matter what starter or theme I use, the same thing always happens to me. Any solution? |
Exactly the same for me. Would also like some solution for this (although it doesn't seem mission critical at this point as this only happens on my development Windows machine and not in my CI, so my production release cycle is not affected in any way). |
|
Same issue here, I have been pressing ctrl + c. On Windows 10, gatsby-cli 2.17.0, and node 14.15.3 |
|
Latest Gatsby(v2.30) updated to ink@v3. I'm curios if anyone could update and test to see if this has resolved the issue. |
I'll give it a test over the next few days. I have updated all my packages now and done a gatsby clean. |
|
I can confirm that I no longer see this issue happening after upgrading to the latest version. Thank you! |
|
same here |
|
@moonmeister Looked good yesterday after updating to gatsby@2.30.1. But today I've had a change in
edit: It does not happen after every config change though, so I can't reliably reproduce it. |
|
You mind sharing what you changed? and in you experience does it matter
what you change in config, or is it anything?
Alex
…On 1/7/2021 6:36 AM, henrik-m wrote:
@moonmeister <https://github.com/moonmeister> Looked good yesterday
after updating to ***@***.*** But today I've had a change in
|gatsby-config.js| and am experiencing the issue again unfortunately.
|gatsby develop| stalls on |onPostBootstrap/Build manifest and related
icons| in first build after config-change. Killing the process and
re-issuing the command runs successfully to the end. Which is how it's
always been for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#25216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAU2W535ZHYQFMD23VXBJUTSYWTFNANCNFSM4OFGMDTA>.
|
|
I added a require to another (dependency-less) JS file containing additional config variables. I used them to change a few options for the plugin I undid and redid the changes, did a production build in between, but have not been able to reproduce the issue yet. It seems to have been a "first build of the day" thing so far. So the situation has definitely improved. I was getting this a lot more often in the past. |
|
I am also getting the issue For me, the issue seems to disappear if I choose a png as a source file instead of an svg |
|
I think it's better, sometimes you do just have to wait a bit for the re-building to happen around 10s for minor CSS changes. |
|
I've been facing the same issue on Windows (stuck on onPostBootstrap & Build manifest and related icons), but largely ignore it because I just hit Ctrl+C and run it again (which works all the time). I am using an svg instead of a png for the icon. It is not a big deal, but kinda annoying since I have to hit Ctrl+C to get it to work in dev. gatsby-config.js output: |
|
I am also facing the same issue when trying to run I've tried almost all of the fixes suggested above, but still facing the issue. Also, in my case the process is stuck at |
|
Same issue here - develop fails the first time, then runs after ctrl-c. |
|
i am have in the same issue |
This solution helped me also. I updated gatsby-cli, removed the node_modules, .cache, public folders and the package-lock.json file. After that I ran a clean npm install. |
|
I'm having the same problem on Windows 10, but it doesn't always happen. Sometimes it does, sometimes it doesn't. But what does fix it is commenting out this code block of the {
resolve: 'gatsby-plugin-manifest',
options: {
name: config.siteTitle,
short_name: config.siteTitleShort,
description: config.siteDescription,
start_url: validatedPathPrefix,
background_color: config.backgroundColor,
theme_color: config.themeColor,
display: 'minimal-ui',
icon: 'static/favicon.svg'
}
}, |
Steps to reproduce
ResultEnvironment
yarn.lock package.json What I've tried
References: @28development/gatsby-source-gitlab-api#1, @gatsbyjs/gatsby#17131, @gatsbyjs/gatsby#28632 |
|
This issue is driving me crazy, two thirds of my attempts to do Commenting out the SVG icon for the manifest plugin fixes this issue, but I need it for production builds. Seems to happen on Windows 10 but not on Ubuntu server 🤷 |
|
For me this workaround from issue #31878 works. I was hoping it was fixed in the latest version of Gatsby, but the problem just moved from production build to development build. // gatsby-node.js
// TODO: temporary workaround for https://github.com/gatsbyjs/gatsby/issues/31878
exports.onCreateWebpackConfig = ({ actions, plugins, stage, getConfig }) => {
// override config only during production JS & CSS build
if (stage === "build-javascript") {
// get current webpack config
const config = getConfig();
const options = {
minimizerOptions: {
preset: [
`default`,
{
svgo: {
full: true,
plugins: [
// potentially destructive plugins removed - see https://github.com/gatsbyjs/gatsby/issues/15629
// use correct config format and remove plugins requiring specific params - see https://github.com/gatsbyjs/gatsby/issues/31619
`removeUselessDefs`,
`cleanupAttrs`,
`cleanupEnableBackground`,
`cleanupIDs`,
`cleanupListOfValues`,
`cleanupNumericValues`,
`collapseGroups`,
`convertColors`,
`convertPathData`,
`convertStyleToAttrs`,
`convertTransform`,
`inlineStyles`,
`mergePaths`,
`minifyStyles`,
`moveElemsAttrsToGroup`,
`moveGroupAttrsToElems`,
`prefixIds`,
`removeAttrs`,
`removeComments`,
`removeDesc`,
// `removeDimensions`,
`removeDoctype`,
`removeEditorsNSData`,
`removeEmptyAttrs`,
`removeEmptyContainers`,
`removeEmptyText`,
`removeHiddenElems`,
`removeMetadata`,
`removeNonInheritableGroupAttrs`,
`removeOffCanvasPaths`,
`removeRasterImages`,
`removeScriptElement`,
`removeStyleElement`,
`removeTitle`,
`removeUnknownsAndDefaults`,
`removeUnusedNS`,
`removeUselessStrokeAndFill`,
`removeXMLProcInst`,
`reusePaths`,
`sortAttrs`,
],
},
},
],
},
};
// find CSS minimizer
const minifyCssIndex = config.optimization.minimizer.findIndex(
(minimizer) => minimizer.constructor.name === "CssMinimizerPlugin"
);
// if found, overwrite existing CSS minimizer with the new one
if (minifyCssIndex > -1) {
config.optimization.minimizer[minifyCssIndex] =
plugins.minifyCss(options);
}
// replace webpack config with the modified object
actions.replaceWebpackConfig(config);
}
}; |
|
I was still running into this issue this morning and I simply renamed the svg file and updated the reference in the manifest and it has completely resolved the issue. Why this resolves the issue? No clue... but it does work 100% of the time now when I was previously deploying with less than a 50% success rate. Hopefully this will help folks figure out the underlying issue. |
and others
Hello guys. I used Solus OS (linux) and gatsby worked just fine without any problem. Now I'm using Windows 10 (x64). Everything I type "gatsby develop" the first time after turning on my computer, it stucks right here:
And I have to Ctrl+C and then "gatsby develop" again and it works. Always stucks at the first time.
The text was updated successfully, but these errors were encountered: