Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

npm WARN deprecated [email protected]: The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`

Ouverte
#34 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
20/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
docker, docker-compose, graphql, node.js, typescript
Domaine
build-system, devops

Piste de recherche

Le rapport mentionne Dockerfile, docker-compose.yml, package*.json et l’étape npm ci. Commencez par reproduire docker compose up et examinez le runtime Node 18, les avertissements du moteur de dépendances, le message obsolète de subscriptions-transport-ws et l’échec ECONNRESET. La tâche sera considérée comme terminée lorsque le build documenté du projet s’achèvera avec succès, mais l’issue ne précise pas quel avertissement ou quel échec doit être traité.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement good first issue help wanted

22.84 npm WARN deprecated [email protected]: The subscriptions-transport-ws package is no longer maintained. We recommend you use graphql-ws instead. For help migrating Apollo software to graphql-ws, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscr

C:\Users\ALI\Projects\SIEMGraphQLTS>docker compose up
time="2025-05-10T11:38:16+03:30" level=warning msg="C:\\Users\\ALI\\Projects\\SIEMGraphQLTS\\docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
[+] Running 23/23
 ✔ postgres Pulled                                                                                                                                     210.2s
   ✔ f18232174bc9 Already exists                                                                                                                         0.0s
   ✔ d76ac568c4ed Pull complete                                                                                                                          1.8s
   ✔ 0110602b32dc Pull complete                                                                                                                          4.1s
   ✔ eeb50695e0e7 Pull complete                                                                                                                          4.2s
   ✔ 8a1f652aba56 Pull complete                                                                                                                          4.2s
   ✔ 3adb38522e0b Pull complete                                                                                                                        206.3s
   ✔ 080b0e04060e Pull complete                                                                                                                        206.3s
   ✔ 1b3cb556b0fe Pull complete                                                                                                                        206.4s
   ✔ b37b6417bdba Pull complete                                                                                                                        206.5s
   ✔ ba81f91243b4 Pull complete                                                                                                                        206.5s
   ✔ b39e65d1a4db Pull complete                                                                                                                        206.6s
 ✔ elasticsearch Pulled                                                                                                                                860.9s
   ✔ 687445115499 Pull complete                                                                                                                         87.2s
   ✔ ecfe4c13e56a Pull complete                                                                                                                         87.9s
   ✔ 03e90c7c247a Pull complete                                                                                                                         88.0s
   ✔ 89732bc75041 Pull complete                                                                                                                         88.0s
   ✔ 8bcd7b94eacb Pull complete                                                                                                                        855.7s
   ✔ 536262d4f9e3 Pull complete                                                                                                                        855.8s
   ✔ 6782ea0d9145 Pull complete                                                                                                                        855.8s
   ✔ 27efb60d30f5 Pull complete                                                                                                                        855.9s
   ✔ 9f2c4c101d6b Pull complete                                                                                                                        855.9s
   ✔ 3d2cef2d2fa5 Pull complete                                                                                                                        856.0s
Compose now can delegate build to bake for better performances
Just set COMPOSE_BAKE=true
[+] Building 83.6s (9/17)                                                                                                                docker:desktop-linux
 => [siem internal] load build definition from Dockerfile                                                                                                0.0s
 => => transferring dockerfile: 889B                                                                                                                     0.0s
 => WARN: FromAsCasing: 'As' and 'FROM' keywords' casing do not match (line 3)                                                                           0.0s
 => WARN: FromAsCasing: 'As' and 'FROM' keywords' casing do not match (line 20)                                                                          0.0s
 => WARN: FromAsCasing: 'As' and 'FROM' keywords' casing do not match (line 41)                                                                          0.0s
 => [siem internal] load metadata for docker.io/library/node:18-alpine3.17                                                                               4.2s
 => [siem auth] library/node:pull token for registry-1.docker.io                                                                                         0.0s
 => [siem internal] load .dockerignore                                                                                                                   0.0s
 => => transferring context: 2B                                                                                                                          0.0s
 => [siem development 1/6] FROM docker.io/library/node:18-alpine3.17@sha256:6239c8a63890ed145ae719574112bc2e37e839a56323bef8d292a579102cdfc2            52.5s
 => => resolve docker.io/library/node:18-alpine3.17@sha256:6239c8a63890ed145ae719574112bc2e37e839a56323bef8d292a579102cdfc2                              0.0s
 => => sha256:36719193de430a308ac0daff3645d4d51da9799574a596765ab55b6fe89a1605 7.14kB / 7.14kB                                                           0.0s
 => => sha256:1207c741d8c9b028d98c4006013f9de959da3c55f85b91ed5e4583438a0112ca 3.38MB / 3.38MB                                                           6.0s
 => => sha256:c44c11c253b80b61ee94b89a630a1d37208c78d4e6b290504dbce5a4e5e4e413 40.11MB / 40.11MB                                                        50.4s
 => => sha256:6239c8a63890ed145ae719574112bc2e37e839a56323bef8d292a579102cdfc2 1.43kB / 1.43kB                                                           0.0s
 => => sha256:25300baedcc0a745be24551f23871a20cfefd19998330c441c453d6a8467e511 1.16kB / 1.16kB                                                           0.0s
 => => sha256:b70131bf260bf40482a7cee1f0ee220b033fed4a0c65e9e313371cff6c3b8283 2.34MB / 2.34MB                                                          11.1s
 => => extracting sha256:1207c741d8c9b028d98c4006013f9de959da3c55f85b91ed5e4583438a0112ca                                                                0.3s
 => => sha256:8483f35fc68629ca371e09ec56eb7505cab2593fc3f4cf7e9bcd65a771408c61 452B / 452B                                                               6.6s
 => => extracting sha256:c44c11c253b80b61ee94b89a630a1d37208c78d4e6b290504dbce5a4e5e4e413                                                                1.7s
 => => extracting sha256:b70131bf260bf40482a7cee1f0ee220b033fed4a0c65e9e313371cff6c3b8283                                                                0.1s
 => => extracting sha256:8483f35fc68629ca371e09ec56eb7505cab2593fc3f4cf7e9bcd65a771408c61                                                                0.0s
 => [siem internal] load build context                                                                                                                  30.3s
 => => transferring context: 353.73MB                                                                                                                   30.1s
 => [siem development 2/6] WORKDIR /usr/src/app                                                                                                          0.2s
 => [siem development 3/6] COPY --chown=node:node package*.json ./                                                                                       0.2s
 => ERROR [siem development 4/6] RUN npm ci                                                                                                             24.6s
------
 > [siem development 4/6] RUN npm ci:
1.750 npm WARN EBADENGINE Unsupported engine {
1.750 npm WARN EBADENGINE   package: '@nestjs/[email protected]',
1.750 npm WARN EBADENGINE   required: { node: '>= 20' },
1.750 npm WARN EBADENGINE   current: { node: 'v18.19.0', npm: '10.2.3' }
1.750 npm WARN EBADENGINE }
1.756 npm WARN EBADENGINE Unsupported engine {
1.756 npm WARN EBADENGINE   package: '[email protected]',
1.756 npm WARN EBADENGINE   required: { node: '>=20' },
1.756 npm WARN EBADENGINE   current: { node: 'v18.19.0', npm: '10.2.3' }
1.756 npm WARN EBADENGINE }
22.84 npm WARN deprecated [email protected]: The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws    For general help using `graphql-ws`, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md
24.21 npm notice
24.21 npm notice New major version of npm available! 10.2.3 -> 11.3.0
24.21 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v11.3.0>
24.21 npm notice Run `npm install -g [email protected]` to update!
24.21 npm notice
24.21 npm ERR! code ECONNRESET
24.21 npm ERR! network aborted
24.21 npm ERR! network This is a problem related to network connectivity.
24.21 npm ERR! network In most cases you are behind a proxy or have bad network settings.
24.21 npm ERR! network
24.21 npm ERR! network If you are behind a proxy, please make sure that the
24.21 npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
24.23
24.23 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2025-05-10T08_23_37_693Z-debug-0.log
------
failed to solve: process "/bin/sh -c npm ci" did not complete successfully: exit code: 1
Langage dominant
TypeScript
Étoiles
2
Forks
2
Merge moyen
17 h 57 min
PR mergées (30 j)
12

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.