You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first thought before any in-depth investigation is that it pulls latest version of eslint, yet sticks to a given version of node; eventually node version became outdated in regard to the eslint one and this triggered. Could be as simple as updating the dockerfile to point to more up-to-date packages.
The text was updated successfully, but these errors were encountered:
Probably the upgrade shouldn't be done like that, but pointing the dockerfile to the right/supported node image version -- if it is the case that the docker image is referencing older nodejs version.
Currently running the command in a clean repo results in this:
Command: docker run -it --rm -v $(pwd)/site:/site -p 8000:8000 aripalo/gatsby-docker develop
Result:
The first thought before any in-depth investigation is that it pulls latest version of eslint, yet sticks to a given version of node; eventually node version became outdated in regard to the eslint one and this triggered. Could be as simple as updating the dockerfile to point to more up-to-date packages.
The text was updated successfully, but these errors were encountered: