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

Investigate on errors and warnings #21

Closed
sogibot opened this issue Nov 14, 2019 · 1 comment
Closed

Investigate on errors and warnings #21

sogibot opened this issue Nov 14, 2019 · 1 comment
Labels
chore Side task

Comments

@sogibot
Copy link
Contributor

sogibot commented Nov 14, 2019

During build-image

npm WARN [email protected] No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

and

info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.

During make start-image && docker logs sogilis_blog

Failed to load external module @babel/register

and

npm WARN [email protected] requires a peer of webpack@^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>= 16.8 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of redux@^2.0.0 || ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of slate@^0.32.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of slate@^0.33.3 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
@jibidus jibidus added the chore Side task label Nov 29, 2019
@JulioJu
Copy link
Contributor

JulioJu commented May 10, 2020

@jibidus

À l'heure d'aujourd'hui il nous reste les erreurs :

julioprayer@vostroarch: ~/Blog master [13:13:26]
$ yarn install
yarn install v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-util@^2.1
.3-beta.0".
warning "netlify-cms > netlify-cms-app > [email protected]" has unmet peer dependency "netlify-cms-lib-
widgets@^1.0.0".
warning "netlify-cms > netlify-cms-app > netlify-cms-core > redux-notifications > [email protected]" has incorrect pee
r dependency "redux@^2.0.0 || ^3.0.0".
[4/4] Building fresh packages...
Done in 24.52s.

Cf. decaporg/decap-cms#1678

Nous avons notamment

Just FYI -- this is something we want to fix if possible, but it isn't actually causing any problems, so it may take a while as we work on other priorities.

Même si tous ne sont pas d'accord. Bref, pas de fixes cool à l'heure actuelle. Et ça semble superflus.

@jibidus , je clos donc.

@JulioJu JulioJu closed this as completed May 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Side task
Projects
None yet
Development

No branches or pull requests

3 participants