• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Register
  • Login
Bagisto Forum

Bagisto

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

Edit Vue.js

General Discussion
3
6
1.3k
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.
  • S
    Shirah last edited by 11 Nov 2020, 03:26

    Hi can I know whether I can edit the card-list.vue file? If it can, mind to share what the step is?

    1 Reply Last reply Reply Quote 0
    • devansh-webkul
      devansh-webkul last edited by 11 Nov 2020, 13:50

      Hi @Shirah,

      Yeah! You can edit it according to your needs.

      Just go to packages/Velocity and run the command npm run watch, this will check your changes and will automatically place all your changes to the public path on saving. Once done just run command npm run prod to compile assets and then publish your packages by using php artisan vendor:publish --force.

      1 Reply Last reply Reply Quote 0
      • 9 months later
      • R
        rahulanand84 last edited by 28 Jul 2021, 19:07

        watch
        cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

        The system cannot find the path specified.
        node:events:371
        throw er; // Unhandled 'error' event
        ^

        Error: spawn node_modules\webpack\bin\webpack.js ENOENT
        at notFoundError (C:\Users\rahul\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:6:26)
        at verifyENOENT (C:\Users\rahul\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:40:16)
        at ChildProcess.cp.emit (C:\Users\rahul\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:27:25)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
        Emitted 'error' event on ChildProcess instance at:
        at ChildProcess.cp.emit (C:\Users\rahul\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:30:37)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
        code: 'ENOENT',
        errno: 'ENOENT',
        syscall: 'spawn node_modules\webpack\bin\webpack.js',
        path: 'node_modules\webpack\bin\webpack.js',
        spawnargs: [
        '--watch',
        '--progress',
        '--hide-modules',
        '--config=node_modules/laravel-mix/setup/webpack.config.js'
        ]
        }

        Getting above error when running the command. What is the issue can you explain and help?

        1 Reply Last reply Reply Quote 0
        • devansh-webkul
          devansh-webkul last edited by 29 Jul 2021, 04:13

          @rahulanand84 said in Edit Vue.js:

          The

          Hi @rahulanand84,

          What comand are you running and on which package you are running?

          1 Reply Last reply Reply Quote 0
          • 12 days later
          • R
            rahulanand84 last edited by 10 Aug 2021, 14:33

            1. I navigated to "Packages/Webkul/Velocity" and ran "npm install"
            2. Then I ran "npm run watch" and made all the changes in the UI vue component
              nothing is reflecting in the command prompt
            3. Finally I ran "npm run production" and it ran successfully.
            4. I rand vendor:publish command too

            after all this nothing worked. Changes were not reflecting on the website.

            1 Reply Last reply Reply Quote 0
            • devansh-webkul
              devansh-webkul last edited by devansh-webkul 11 Aug 2021, 04:13 11 Aug 2021, 04:12

              Till 3rd point, it's all right. But on the fourth point you need to use --force flag to see the changes.

              But make sure you have not customized something big otherwise your changes got reverted.

              I suggest you to places the file manually in the resources/themes path.

              1 Reply Last reply Reply Quote 1
              4 out of 6
              • First post
                4/6
                Last post