Bagisto Forum

    Bagisto

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    How prevent error vite manifest on custom theme

    General Discussion
    2
    4
    588
    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.
    • A
      alexVillalobos last edited by

      Hello, I have already installed the custom theme and configured it appropriately, but what is happening?
      When I open the website it asks me for the vite manifest
      I understand that this is resolved by npm run dev and the error disappears but if I do an npm run build the error is still there so how can I remove the aforementioned error when I upload it to production the store any ideas

      1 Reply Last reply Reply Quote 0
      • Rishabh-Webkul
        Rishabh-Webkul last edited by

        Hello @alexVillalobos

        Greetings of the day..!!

        There is no other way to include this because if you make any kind of changes and save the file it doesn't get compiled npm run dev helps to compile all those changes so after the changes are reflected you don't need to run npm run build again because the build is already present in it.

        So overall If you run the npm run build again you have to run npm run dev to compile all the changes.

        Kindly check our custom theme blog and video tutorial here.

        https://bagisto.com/en/create-custom-theme-in-bagisto/

        https://youtu.be/K3FdBDsXAH8?si=eXaG8kyrdLs1zeTM

        Thanks & Regards..!!

        A 1 Reply Last reply Reply Quote 0
        • A
          alexVillalobos @Rishabh-Webkul last edited by

          @Rishabh-Webkul Once the changes have been made and compiled with npm run build then why should I have npm run dev up? Yes, in theory I already have the change in the build. I am referring to already having everything customized because I should continue maintaining npm run dev. Yes with the build. I would avoid that, since on the production server I should not execute this command

          A 1 Reply Last reply Reply Quote 0
          • A
            alexVillalobos @alexVillalobos last edited by

            @alexVillalobos said in How prevent error vite manifest on custom theme:

            @Rishabh-Webkul Once the changes have been made and compiled with npm run build then why should I have npm run dev up? Yes, in theory I already have the change in the build. I am referring to already having everything customized because I should continue maintaining npm run dev. Yes with the build. I would avoid that, since on the production server I should not execute this command

            I already deployed in production but I have the same problem with the vite manifest, in production it is not valid to use npm run dev since it is for the development environment, any idea, because I did the vendor:publish --force and I also ran npm run build but it keeps requesting he vite manifested.
            At this point is it also required to keep npm run dev on the air?

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