Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gatsby is failed at production Javascript and CSS #38977

Open
2 tasks done
rathoreyaduvendrasingh opened this issue May 16, 2024 · 1 comment
Open
2 tasks done

Gatsby is failed at production Javascript and CSS #38977

rathoreyaduvendrasingh opened this issue May 16, 2024 · 1 comment
Labels
status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer type: bug An issue or pull request relating to a bug in Gatsby

Comments

@rathoreyaduvendrasingh
Copy link

Preliminary Checks

Description

when i upgrade the gatsby version from 4.1.1 to to 4.20.0 the gatsby build failed at Building production JavaScript and CSS bundles and didn' t show any error why did the build failed. I also tried to get the issue. I found out that the build is working fine till 4.6.0 and started failing at 4.6.1 .

Reproduction Link

can't provide the link

Steps to Reproduce

Version upgrade from 4.1.1 to 4.20.0

Expected Result

wanted the build to be executed successfully

Actual Result

Screenshot 2024-05-16 at 12 38 37 PM

Environment

> gatsby info --clipboard


  System:
    OS: macOS 13.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm
  Browsers:
    Chrome: 125.0.6422.60
    Safari: 16.2
  npmPackages:
    gatsby: 4.20.0 => 4.20.0
    gatsby-cli: ^4.19.0 => 4.25.0
    gatsby-image: ^2.2.39 => 2.11.0
    gatsby-plugin-asset-path: ^3.0.1 => 3.0.4
    gatsby-plugin-google-tagmanager: 4.25.0 => 4.25.0
    gatsby-plugin-newrelic: 2.6.0 => 2.6.0
    gatsby-plugin-react-helmet: ^5.25.0 => 5.25.0
    gatsby-plugin-react-next: ^1.0.11 => 1.0.11
    gatsby-plugin-react-svg: ^3.3.0 => 3.3.0
    gatsby-plugin-remove-fingerprints: ^0.0.2 => 0.0.2
    gatsby-plugin-root-import: ^2.0.8 => 2.0.9
    gatsby-plugin-sass: ^5.25.0 => 5.25.0
    gatsby-plugin-webpack-bundle-analyser-v2: ^1.1.32 => 1.1.32
    gatsby-plugin-workerize-loader: ^2.1.0 => 2.1.0
    gatsby-source-graphql: ^4.25.0 => 4.25.0
  npmGlobalPackages:
    gatsby-cli: 5.13.3

Config Flags

No response

@rathoreyaduvendrasingh rathoreyaduvendrasingh added the type: bug An issue or pull request relating to a bug in Gatsby label May 16, 2024
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 16, 2024
@andriy-f
Copy link

There's gatsby v5 already. it may be not a trivial thing to upgrade but they probably won't be fixing v4 anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
Development

No branches or pull requests

2 participants