HelloWord Sharepoint Framework

  • HelloWord Sharepoint Framework

    Posté par julio sur 14 novembre 2024 à 7h59

    Bonjour, je souhaite créer mon premier helloword avec SharePoint Framework toutefois lorsque j’ai essayé d’installer mon générateur SharePoint avec la commande :

    npm install @microsoft/generator-sharepoint –global

    J’obtiens plutôt ces messages :

    npm warn deprecated osenv@0.1.5: This package is no longer suported.
    npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
    npm warn deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
    npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
    npm warn deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
    npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
    npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
    npm warn deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
    npm warn deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
    npm warn deprecated uuid@3.1.0: 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.
    npm warn deprecated uuid@2.0.3: 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.

    Après quelques lectures sur les forums j’ai cru comprendre que ce message est dû au faite que mes Library sont obsolètes par rapport à la version et j’ai cru comprendre que l’on peut résoudre ce problème avec cette commande : npm i -g npm npm i -g nativescript@next Or lui aussi me produit plutôt ce message d’échec

    npm warn deprecated osenv@0.1.5: This package is no longer supported.
    npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
    npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
    npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
    npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
    npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
    npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
    npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
    npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
    npm warn deprecated npmlog@6.0.2: This package is no longer supported.
    npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
    npm warn deprecated gauge@4.0.4: This package is no longer supported.
    npm warn deprecated read-package-json@6.0.4: This package is no longer supported. Please use @npmcli/package-json instead.
    npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
    npm warn deprecated
    npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
    npm warn deprecated @xmldom/xmldom@0.7.13: this version is no longer supported, please update to at least 0.8.*
    npm warn deprecated osenv@0.1.4: This package is no longer supported.
    npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported

    Alors j’aimerais bien savoir comment faire et savoir pourquoi ça ne marche pas. Merci encore tous

    julio a répondu Il y a 1 semaine, 2 jours 1 Membre · 0 Réponses
  • 0 Réponses

Désolé, aucune réponse n’a été trouvée.

Connectez-vous pour répondre.