XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    'yarn build' failure

    Scheduled Pinned Locked Moved Xen Orchestra
    19 Posts 5 Posters 1.8k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • julien-fJ Offline
      julien-f Vates 🪐 Co-Founder XO Team @Danp
      last edited by

      Indeed, due to conversion of xo-server to ES modules, Node 14.17 is now required.

      I've just updated the docs to clarify that we target latest Node LTS.

      julien-fJ 1 Reply Last reply Reply Quote 0
      • julien-fJ Offline
        julien-f Vates 🪐 Co-Founder XO Team @julien-f
        last edited by

        I confirm an issue with xo-web though, investigating…

        A 1 Reply Last reply Reply Quote 0
        • A Offline
          AlexD2006 @julien-f
          last edited by

          @julien-f : thx for investigating.

          Tried a fresh install half of the day with the same error and thought i am doing something wrong.
          Then i tried updateing a running installation and hit the same error.

          I keep investigating by myself too.

          julien-fJ 1 Reply Last reply Reply Quote 0
          • julien-fJ Offline
            julien-f Vates 🪐 Co-Founder XO Team @AlexD2006
            last edited by

            Should now be fixed, sorry for this.

            A 1 Reply Last reply Reply Quote 2
            • M Offline
              Meth0d @ci4ic4
              last edited by

              @ci4ic4 how did you manage to update from 14.16 to 14.17 on Debian 10?

              deb.nodesource.com/setup_14.x just seems to give me 14.16

              DanpD C 2 Replies Last reply Reply Quote 0
              • DanpD Offline
                Danp Pro Support Team @Meth0d
                last edited by

                @meth0d I use n lts to install the correct version

                M 1 Reply Last reply Reply Quote 1
                • M Offline
                  Meth0d @Danp
                  last edited by

                  @danp Thanks that worked.

                  @julien-f yes seems fixed, thanks.

                  1 Reply Last reply Reply Quote 0
                  • C Offline
                    ci4ic4 @Meth0d
                    last edited by

                    @meth0d See the reference sequence provided in the original post. As I said, my reason to go to Buster was my inability to upgrade to nodejs 14.17.

                    1 Reply Last reply Reply Quote 0
                    • C Offline
                      ci4ic4
                      last edited by

                      Builds now, thanks for the quick response.

                      1 Reply Last reply Reply Quote 0
                      • A Offline
                        AlexD2006 @julien-f
                        last edited by

                        @julien-f
                        thx for the quick fix. works perfectly now.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post