Global installation with npm : @latest version not recommended for global scope?












0















I recently heard discussion between developers that I didn't understand :
For npm module installation, @latest tag should not be used with --global option because, with any update it could cause some trouble. Conclusion was : @latest can be used peacefully for local installation but a specific version is preferred for global installation.
But I didn't understand explanation.










share|improve this question

























  • PS : begin of post is truncated even when editing so : Hello everyone

    – logos
    Aug 10 '17 at 15:42













  • PPS : it is for angular installation

    – logos
    Aug 10 '17 at 15:51
















0















I recently heard discussion between developers that I didn't understand :
For npm module installation, @latest tag should not be used with --global option because, with any update it could cause some trouble. Conclusion was : @latest can be used peacefully for local installation but a specific version is preferred for global installation.
But I didn't understand explanation.










share|improve this question

























  • PS : begin of post is truncated even when editing so : Hello everyone

    – logos
    Aug 10 '17 at 15:42













  • PPS : it is for angular installation

    – logos
    Aug 10 '17 at 15:51














0












0








0








I recently heard discussion between developers that I didn't understand :
For npm module installation, @latest tag should not be used with --global option because, with any update it could cause some trouble. Conclusion was : @latest can be used peacefully for local installation but a specific version is preferred for global installation.
But I didn't understand explanation.










share|improve this question
















I recently heard discussion between developers that I didn't understand :
For npm module installation, @latest tag should not be used with --global option because, with any update it could cause some trouble. Conclusion was : @latest can be used peacefully for local installation but a specific version is preferred for global installation.
But I didn't understand explanation.







npm npm-install






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 12 '17 at 4:18









Cœur

18.4k9109148




18.4k9109148










asked Aug 10 '17 at 15:38









logoslogos

1




1













  • PS : begin of post is truncated even when editing so : Hello everyone

    – logos
    Aug 10 '17 at 15:42













  • PPS : it is for angular installation

    – logos
    Aug 10 '17 at 15:51



















  • PS : begin of post is truncated even when editing so : Hello everyone

    – logos
    Aug 10 '17 at 15:42













  • PPS : it is for angular installation

    – logos
    Aug 10 '17 at 15:51

















PS : begin of post is truncated even when editing so : Hello everyone

– logos
Aug 10 '17 at 15:42







PS : begin of post is truncated even when editing so : Hello everyone

– logos
Aug 10 '17 at 15:42















PPS : it is for angular installation

– logos
Aug 10 '17 at 15:51





PPS : it is for angular installation

– logos
Aug 10 '17 at 15:51












1 Answer
1






active

oldest

votes


















1














@latest is used to override any versions listed as dependencies within your package.json.



You shouldn't have a global package.json and therefore there isn't a reason to use @latest because npm install will install the latest version by default.



npm install docs:




npm install [<@scope>/]<name>:



Do a <name>@<tag> install, where <tag> is the "tag" config. (See npm-config. The config's default value is latest.)



In most cases, this will install the version of the modules tagged as latest on the npm registry.







share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f45618071%2fglobal-installation-with-npm-latest-version-not-recommended-for-global-scope%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    @latest is used to override any versions listed as dependencies within your package.json.



    You shouldn't have a global package.json and therefore there isn't a reason to use @latest because npm install will install the latest version by default.



    npm install docs:




    npm install [<@scope>/]<name>:



    Do a <name>@<tag> install, where <tag> is the "tag" config. (See npm-config. The config's default value is latest.)



    In most cases, this will install the version of the modules tagged as latest on the npm registry.







    share|improve this answer






























      1














      @latest is used to override any versions listed as dependencies within your package.json.



      You shouldn't have a global package.json and therefore there isn't a reason to use @latest because npm install will install the latest version by default.



      npm install docs:




      npm install [<@scope>/]<name>:



      Do a <name>@<tag> install, where <tag> is the "tag" config. (See npm-config. The config's default value is latest.)



      In most cases, this will install the version of the modules tagged as latest on the npm registry.







      share|improve this answer




























        1












        1








        1







        @latest is used to override any versions listed as dependencies within your package.json.



        You shouldn't have a global package.json and therefore there isn't a reason to use @latest because npm install will install the latest version by default.



        npm install docs:




        npm install [<@scope>/]<name>:



        Do a <name>@<tag> install, where <tag> is the "tag" config. (See npm-config. The config's default value is latest.)



        In most cases, this will install the version of the modules tagged as latest on the npm registry.







        share|improve this answer















        @latest is used to override any versions listed as dependencies within your package.json.



        You shouldn't have a global package.json and therefore there isn't a reason to use @latest because npm install will install the latest version by default.



        npm install docs:




        npm install [<@scope>/]<name>:



        Do a <name>@<tag> install, where <tag> is the "tag" config. (See npm-config. The config's default value is latest.)



        In most cases, this will install the version of the modules tagged as latest on the npm registry.








        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 15 '18 at 4:54

























        answered May 8 '18 at 0:27









        JBallinJBallin

        1,0641120




        1,0641120
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f45618071%2fglobal-installation-with-npm-latest-version-not-recommended-for-global-scope%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Xamarin.iOS Cant Deploy on Iphone

            Glorious Revolution

            Dulmage-Mendelsohn matrix decomposition in Python