Typescript: Navigator merging with lib.d.ts












1














I'm confused about merging with lib.d.ts. I am trying to add a property to Navigator. I think I need to merge with Navigator interface that is declared in lib.d.ts. I am using TS 2.0.6.



Here is my code:



let lang = navigator.language || navigator.userLanguage; 


Which produces this error:




Property 'userLanguage' does not exist on type 'Navigator'.




I've tried making a merge happen this way:



interface Navigator {
userLanguage: string;
}


But, still cannot find the userLanguage property...



Can someone help me understand where and how I can merge with lib.d.ts declarations?



Thank-you










share|improve this question






















  • Have you really loaded file containing interface Navigator by compilator/IDE? Try to add link pointing to file containing Interface Navigator in header of file where extended object is used by comment like /// <reference path="Navigator.ts" />. Playground don't highlight error too.
    – Misaz
    Nov 2 '16 at 17:28


















1














I'm confused about merging with lib.d.ts. I am trying to add a property to Navigator. I think I need to merge with Navigator interface that is declared in lib.d.ts. I am using TS 2.0.6.



Here is my code:



let lang = navigator.language || navigator.userLanguage; 


Which produces this error:




Property 'userLanguage' does not exist on type 'Navigator'.




I've tried making a merge happen this way:



interface Navigator {
userLanguage: string;
}


But, still cannot find the userLanguage property...



Can someone help me understand where and how I can merge with lib.d.ts declarations?



Thank-you










share|improve this question






















  • Have you really loaded file containing interface Navigator by compilator/IDE? Try to add link pointing to file containing Interface Navigator in header of file where extended object is used by comment like /// <reference path="Navigator.ts" />. Playground don't highlight error too.
    – Misaz
    Nov 2 '16 at 17:28
















1












1








1







I'm confused about merging with lib.d.ts. I am trying to add a property to Navigator. I think I need to merge with Navigator interface that is declared in lib.d.ts. I am using TS 2.0.6.



Here is my code:



let lang = navigator.language || navigator.userLanguage; 


Which produces this error:




Property 'userLanguage' does not exist on type 'Navigator'.




I've tried making a merge happen this way:



interface Navigator {
userLanguage: string;
}


But, still cannot find the userLanguage property...



Can someone help me understand where and how I can merge with lib.d.ts declarations?



Thank-you










share|improve this question













I'm confused about merging with lib.d.ts. I am trying to add a property to Navigator. I think I need to merge with Navigator interface that is declared in lib.d.ts. I am using TS 2.0.6.



Here is my code:



let lang = navigator.language || navigator.userLanguage; 


Which produces this error:




Property 'userLanguage' does not exist on type 'Navigator'.




I've tried making a merge happen this way:



interface Navigator {
userLanguage: string;
}


But, still cannot find the userLanguage property...



Can someone help me understand where and how I can merge with lib.d.ts declarations?



Thank-you







typescript typescript-typings typescript2.0






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 2 '16 at 14:10









Thibs

2,42962759




2,42962759












  • Have you really loaded file containing interface Navigator by compilator/IDE? Try to add link pointing to file containing Interface Navigator in header of file where extended object is used by comment like /// <reference path="Navigator.ts" />. Playground don't highlight error too.
    – Misaz
    Nov 2 '16 at 17:28




















  • Have you really loaded file containing interface Navigator by compilator/IDE? Try to add link pointing to file containing Interface Navigator in header of file where extended object is used by comment like /// <reference path="Navigator.ts" />. Playground don't highlight error too.
    – Misaz
    Nov 2 '16 at 17:28


















Have you really loaded file containing interface Navigator by compilator/IDE? Try to add link pointing to file containing Interface Navigator in header of file where extended object is used by comment like /// <reference path="Navigator.ts" />. Playground don't highlight error too.
– Misaz
Nov 2 '16 at 17:28






Have you really loaded file containing interface Navigator by compilator/IDE? Try to add link pointing to file containing Interface Navigator in header of file where extended object is used by comment like /// <reference path="Navigator.ts" />. Playground don't highlight error too.
– Misaz
Nov 2 '16 at 17:28














2 Answers
2






active

oldest

votes


















2














Turns out I did not realize that I had to create a navigator.d.ts file with the interface in it. Once that file was created in my project, errors went away.



I did not need to use the ///< reference ...






share|improve this answer





















  • This worked for me. Thanks Thibs.
    – JaysQubeXon
    May 19 '18 at 9:34



















1














An alternative to creating a type definition file, as in the accepted answer, is to access the "userLanguage" property using a string literal, like so:



navigator['userLanguage'] //=> OK

navigator.userLanguage //=> TS2339: Property ‘userLanguage’ does not exist on type ‘Navigator’





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%2f40382056%2ftypescript-navigator-merging-with-lib-d-ts%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    Turns out I did not realize that I had to create a navigator.d.ts file with the interface in it. Once that file was created in my project, errors went away.



    I did not need to use the ///< reference ...






    share|improve this answer





















    • This worked for me. Thanks Thibs.
      – JaysQubeXon
      May 19 '18 at 9:34
















    2














    Turns out I did not realize that I had to create a navigator.d.ts file with the interface in it. Once that file was created in my project, errors went away.



    I did not need to use the ///< reference ...






    share|improve this answer





















    • This worked for me. Thanks Thibs.
      – JaysQubeXon
      May 19 '18 at 9:34














    2












    2








    2






    Turns out I did not realize that I had to create a navigator.d.ts file with the interface in it. Once that file was created in my project, errors went away.



    I did not need to use the ///< reference ...






    share|improve this answer












    Turns out I did not realize that I had to create a navigator.d.ts file with the interface in it. Once that file was created in my project, errors went away.



    I did not need to use the ///< reference ...







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 2 '16 at 19:58









    Thibs

    2,42962759




    2,42962759












    • This worked for me. Thanks Thibs.
      – JaysQubeXon
      May 19 '18 at 9:34


















    • This worked for me. Thanks Thibs.
      – JaysQubeXon
      May 19 '18 at 9:34
















    This worked for me. Thanks Thibs.
    – JaysQubeXon
    May 19 '18 at 9:34




    This worked for me. Thanks Thibs.
    – JaysQubeXon
    May 19 '18 at 9:34













    1














    An alternative to creating a type definition file, as in the accepted answer, is to access the "userLanguage" property using a string literal, like so:



    navigator['userLanguage'] //=> OK

    navigator.userLanguage //=> TS2339: Property ‘userLanguage’ does not exist on type ‘Navigator’





    share|improve this answer


























      1














      An alternative to creating a type definition file, as in the accepted answer, is to access the "userLanguage" property using a string literal, like so:



      navigator['userLanguage'] //=> OK

      navigator.userLanguage //=> TS2339: Property ‘userLanguage’ does not exist on type ‘Navigator’





      share|improve this answer
























        1












        1








        1






        An alternative to creating a type definition file, as in the accepted answer, is to access the "userLanguage" property using a string literal, like so:



        navigator['userLanguage'] //=> OK

        navigator.userLanguage //=> TS2339: Property ‘userLanguage’ does not exist on type ‘Navigator’





        share|improve this answer












        An alternative to creating a type definition file, as in the accepted answer, is to access the "userLanguage" property using a string literal, like so:



        navigator['userLanguage'] //=> OK

        navigator.userLanguage //=> TS2339: Property ‘userLanguage’ does not exist on type ‘Navigator’






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 19 '18 at 13:48









        sdgluck

        9,66112548




        9,66112548






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f40382056%2ftypescript-navigator-merging-with-lib-d-ts%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

            'app-layout' is not a known element: how to share Component with different Modules

            android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

            WPF add header to Image with URL pettitions [duplicate]