LWC SFDX source push error TypeError: LWC1009: decl.moveTo is not a function





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















Getting a strange error while running the sfdx force:source:push command for an lwc component



enter image description here



PROJECT PATH ERROR
──────────── ─────────────────────────────────────────────────
N/A TypeError: LWC1009: decl.moveTo is not a function










share|improve this question







New contributor




alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



























    2















    Getting a strange error while running the sfdx force:source:push command for an lwc component



    enter image description here



    PROJECT PATH ERROR
    ──────────── ─────────────────────────────────────────────────
    N/A TypeError: LWC1009: decl.moveTo is not a function










    share|improve this question







    New contributor




    alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      2












      2








      2








      Getting a strange error while running the sfdx force:source:push command for an lwc component



      enter image description here



      PROJECT PATH ERROR
      ──────────── ─────────────────────────────────────────────────
      N/A TypeError: LWC1009: decl.moveTo is not a function










      share|improve this question







      New contributor




      alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      Getting a strange error while running the sfdx force:source:push command for an lwc component



      enter image description here



      PROJECT PATH ERROR
      ──────────── ─────────────────────────────────────────────────
      N/A TypeError: LWC1009: decl.moveTo is not a function







      salesforcedx lightning-web-components






      share|improve this question







      New contributor




      alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 5 hours ago









      alcoforadoalcoforado

      414




      414




      New contributor




      alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          3














          I found the issue. The cause is a css file I have in a Lightning Web Component bundle.
          I had two declarations for the same selector in my css



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          }

          .slds-card {
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          Merging them into one solved my issue.



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          I wonder if this should be logged as a bug in sfdx ??






          share|improve this answer








          New contributor




          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





















          • I'd say log a bug. Worse case scenario, they close the bug, but if it's reproducible, they'll likely fix it, or at least document it as a limitation.

            – sfdcfox
            3 hours ago












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "459"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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
          });


          }
          });






          alcoforado is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f256817%2flwc-sfdx-source-push-error-typeerror-lwc1009-decl-moveto-is-not-a-function%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









          3














          I found the issue. The cause is a css file I have in a Lightning Web Component bundle.
          I had two declarations for the same selector in my css



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          }

          .slds-card {
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          Merging them into one solved my issue.



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          I wonder if this should be logged as a bug in sfdx ??






          share|improve this answer








          New contributor




          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





















          • I'd say log a bug. Worse case scenario, they close the bug, but if it's reproducible, they'll likely fix it, or at least document it as a limitation.

            – sfdcfox
            3 hours ago
















          3














          I found the issue. The cause is a css file I have in a Lightning Web Component bundle.
          I had two declarations for the same selector in my css



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          }

          .slds-card {
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          Merging them into one solved my issue.



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          I wonder if this should be logged as a bug in sfdx ??






          share|improve this answer








          New contributor




          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





















          • I'd say log a bug. Worse case scenario, they close the bug, but if it's reproducible, they'll likely fix it, or at least document it as a limitation.

            – sfdcfox
            3 hours ago














          3












          3








          3







          I found the issue. The cause is a css file I have in a Lightning Web Component bundle.
          I had two declarations for the same selector in my css



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          }

          .slds-card {
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          Merging them into one solved my issue.



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          I wonder if this should be logged as a bug in sfdx ??






          share|improve this answer








          New contributor




          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.










          I found the issue. The cause is a css file I have in a Lightning Web Component bundle.
          I had two declarations for the same selector in my css



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          }

          .slds-card {
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          Merging them into one solved my issue.



          .slds-card {
          border: 1px #CFD7E6 solid !important;
          border-radius: 5px !important;
          background-color: #9298eb !important;
          padding-left: 1rem !important;
          padding-right: 1rem !important;
          }


          I wonder if this should be logged as a bug in sfdx ??







          share|improve this answer








          New contributor




          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          share|improve this answer



          share|improve this answer






          New contributor




          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          answered 5 hours ago









          alcoforadoalcoforado

          414




          414




          New contributor




          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





          New contributor





          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.






          alcoforado is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.













          • I'd say log a bug. Worse case scenario, they close the bug, but if it's reproducible, they'll likely fix it, or at least document it as a limitation.

            – sfdcfox
            3 hours ago



















          • I'd say log a bug. Worse case scenario, they close the bug, but if it's reproducible, they'll likely fix it, or at least document it as a limitation.

            – sfdcfox
            3 hours ago

















          I'd say log a bug. Worse case scenario, they close the bug, but if it's reproducible, they'll likely fix it, or at least document it as a limitation.

          – sfdcfox
          3 hours ago





          I'd say log a bug. Worse case scenario, they close the bug, but if it's reproducible, they'll likely fix it, or at least document it as a limitation.

          – sfdcfox
          3 hours ago










          alcoforado is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          alcoforado is a new contributor. Be nice, and check out our Code of Conduct.













          alcoforado is a new contributor. Be nice, and check out our Code of Conduct.












          alcoforado is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Salesforce Stack Exchange!


          • 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%2fsalesforce.stackexchange.com%2fquestions%2f256817%2flwc-sfdx-source-push-error-typeerror-lwc1009-decl-moveto-is-not-a-function%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

          Ponta tanko

          Tantalo (mitologio)

          Erzsébet Schaár