Currently (as of 6ed2f2c) building a Docker image fails with this error:
> [10/11] RUN cd frontend && yarn && yarn build:
#14 0.404 yarn install v1.22.10
#14 0.486 info No lockfile found.
#14 0.511 [1/4] Resolving packages...
#14 1.111 warning @blueprintjs/core > [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
#14 1.111 warning @blueprintjs/core > react-popper > [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
#14 2.952 warning rc-upload > babel-runtime > [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
#14 5.611 warning react-scripts > [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
#14 6.123 warning react-scripts > [email protected]: This loader has been deprecated. Please use eslint-webpack-plugin
#14 6.261 warning react-scripts > [email protected]: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
#14 6.313 warning react-scripts > [email protected]: out of support
#14 6.788 warning react-scripts > [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
#14 6.897 warning react-scripts > babel-core > babel-register > [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
#14 7.481 warning react-scripts > autoprefixer > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
#14 7.715 warning react-scripts > css-loader > cssnano > autoprefixer > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
#14 8.121 warning react-scripts > babel-preset-react-app > babel-preset-env > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
#14 8.718 warning react-scripts > sw-precache-webpack-plugin > [email protected]: Please migrate to Workbox: https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
#14 9.077 warning react-scripts > webpack-dev-server > [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
#14 9.083 warning react-scripts > webpack-dev-server > chokidar > [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
#14 10.03 warning react-scripts > css-loader > cssnano > postcss-merge-rules > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
#14 11.71 warning react-scripts > sw-precache-webpack-plugin > sw-precache > [email protected]: Please migrate to Workbox: https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
#14 12.18 warning react-scripts > webpack-dev-server > sockjs > [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
#14 13.60 warning react-scripts > webpack > watchpack > watchpack-chokidar2 > [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
#14 13.60 warning react-scripts > webpack > watchpack > watchpack-chokidar2 > chokidar > [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
#14 13.67 warning react-scripts > css-loader > cssnano > postcss-merge-rules > caniuse-api > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
#14 14.06 warning react-scripts > eslint > file-entry-cache > flat-cache > [email protected]: CircularJSON is in maintenance only, flatted is its successor.
#14 15.31 warning react-scripts > jest > jest-cli > jest-haste-map > [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
#14 15.50 warning react-scripts > webpack > node-libs-browser > url > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
#14 16.57 warning react-scripts > jest > jest-cli > jest-environment-jsdom > jsdom > [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
#14 16.58 warning react-scripts > jest > jest-cli > jest-environment-jsdom > jsdom > request > [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
#14 17.20 warning react-scripts > webpack-dev-server > chokidar > readdirp > micromatch > snapdragon > source-map-resolve > [email protected]: https://github.com/lydell/resolve-url#deprecated
#14 17.21 warning react-scripts > webpack-dev-server > chokidar > readdirp > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
#14 17.50 warning react-scripts > jest > jest-cli > jest-environment-jsdom > jsdom > request > [email protected]: this library is no longer supported
#14 18.46 [2/4] Fetching packages...
#14 35.22 info [email protected]: The platform "linux" is incompatible with this module.
#14 35.22 info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
#14 35.23 info [email protected]: The engine "node" is incompatible with this module. Expected version ">= 8.10.0". Got "6.17.1"
#14 35.23 info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
#14 35.23 info [email protected]: The platform "linux" is incompatible with this module.
#14 35.23 info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
#14 35.23 info [email protected]: The engine "node" is incompatible with this module. Expected version "^8.16.0 || ^10.6.0 || >=11.0.0". Got "6.17.1"
#14 35.23 info [email protected]: The engine "node" is incompatible with this module. Expected version ">= 8". Got "6.17.1"
#14 35.23 info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
#14 35.23 info [email protected]: The engine "node" is incompatible with this module. Expected version ">=8". Got "6.17.1"
#14 35.23 info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
#14 35.24 info [email protected]: The engine "node" is incompatible with this module. Expected version ">=8.10.0". Got "6.17.1"
#14 35.24 info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
#14 35.24 error [email protected]: The engine "node" is incompatible with this module. Expected version ">=8.0.0". Got "6.17.1"
#14 35.25 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
#14 35.25 error Found incompatible module.
------
executor failed running [/bin/sh -c cd frontend && yarn && yarn build]: exit code: 1
Looks like several dependencies are not going to build/install with NodeJS v6 any more.
If a working yarn.lock file would be part of the repository, it might be possible to mitigate this, as this would specify versions for all indirect dependencies.
Currently (as of 6ed2f2c) building a Docker image fails with this error:
Looks like several dependencies are not going to build/install with NodeJS v6 any more.
If a working
yarn.lockfile would be part of the repository, it might be possible to mitigate this, as this would specify versions for all indirect dependencies.