Closed digitalimplementer closed 10 months ago
Hey @digitalimplementer, can you run the following steps and let me know if you still have the same issues:
development
branchyarn
yarn start
Also, later when you make a PR make sure it's to the development branch as well.
That should work. If you still have issues let me know!
is this something we need to add to README, or is this just user error on part of @digitalimplementer ?
Only the last command changed as we had to add an env var for compatibility reasons when updating node versions (so now it's yarn start
instead of gatsby develop
). That being said, I think it would be valuable to update the README as a couple more things are out of date now so I'll do it 👍
@DzhideX appreciate your prompt attention to the issue. I'm writing to clarify that the error occurred during project startup using both Gatsby CLI and Yarn. If I am not mistaken, yarn start ultimately executes gatsby develop command. To temporarily circumvent the error, I've disabled specific Stylelint rules within the .stylelintrc configuration file. This allowed me to proceed with local project execution.
yarn start ultimately executes gatsby develop command.
Essentially, but yarn start
also adds a node env var (more specifically: "develop": "NODE_OPTIONS=--openssl-legacy-provider gatsby develop"
) that adds support for using a newer node engine (v18).
This allowed me to proceed with local project execution.
Great. If you end up having issues later (e.g. with CI/CD) we can take a better look then 👍
Stylelint's preventing the project from running (errors for the rules "length-zero-no-unit", "declaration-block-trailing-semicolon" and "declaration-block-single-line-max-declarations").