Bagisto Forum

    Bagisto

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

    Velocity css file

    General Discussion
    6
    30
    5676
    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

      To run " npm run prod " inside the velocity package, you mean $root_folder/packages/Webkul/Velocity right?

      1 Reply Last reply Reply Quote 0
      • V
        vishalK last edited by

        Hi @Shirah

        Yes

        Thanks!

        1 Reply Last reply Reply Quote 0
        • S
          Shirah last edited by

          I can't run the npm. I get the npm error.

          The error:
          'npm' is not recognized as an internal or external command,
          operable program or batch file.

          1 Reply Last reply Reply Quote 0
          • V
            Vaishali Agarwal last edited by

            @Shirah
            first run the command

            npm i
            npm run prod

            1 Reply Last reply Reply Quote 0
            • S
              Shirah last edited by

              I still get the same error.

              1 Reply Last reply Reply Quote 0
              • V
                Vaishali Agarwal last edited by

                @Shirah said in Velocity css file:

                'npm' is not recognized as an internal or external command,

                first check that npm must be installed on your system using command

                npm -v
                

                if already installed and showing the error then follow the solution provided here https://stackoverflow.com/questions/20992723/npm-is-not-recognized-as-internal-or-external-command-operable-program-or-bat/47524025

                1 Reply Last reply Reply Quote 0
                • S
                  Shirah last edited by

                  Thank you the problem solve. But now I make changes in the shared.scss files but nothing change.

                  1 Reply Last reply Reply Quote 0
                  • V
                    Vaishali Agarwal last edited by

                    @Shirah
                    make sure you have followed the command in a proper way-

                    run the below command inside package/velocity

                    npm run prod
                    

                    now go to the project root directory and execute below and press the index number of velocity package

                    php artisan vendor:publish --force
                    
                    1 Reply Last reply Reply Quote 0
                    • S
                      Shirah last edited by

                      Still not working. I received other error.

                      npm.PNG

                      1 Reply Last reply Reply Quote 0
                      • R
                        raouf415 last edited by

                        i have exactly the same issues cannot readproperty 'inProduction' any solution ?

                        1 Reply Last reply Reply Quote 0
                        • V
                          Vaishali Agarwal last edited by

                          @raouf415
                          please first check that node and npm should be installed on your system.

                          1 Reply Last reply Reply Quote 0
                          • R
                            raouf415 last edited by raouf415

                            Already installed npm 6.14.8 a node 8.0.0 sorry node 14.15.0

                            1 Reply Last reply Reply Quote 0
                            • R
                              raouf415 last edited by

                              Here is error when test now
                              npm ERR! code ELIFECYCLE
                              npm ERR! errno 1
                              npm ERR! @ 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
                              npm ERR! Exit status 1
                              npm ERR!
                              npm ERR! Failed at the @ watch script.
                              npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

                              npm ERR! A complete log of this run can be found in:
                              npm ERR! /home/raouf/.npm/_logs/2020-11-16T16_31_38_907Z-debug.log

                              1 Reply Last reply Reply Quote 0
                              • V
                                Vaishali Agarwal last edited by

                                @raouf415
                                your application is under dev mode or production mode?

                                R 1 Reply Last reply Reply Quote 0
                                • R
                                  raouf415 last edited by

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • R
                                    raouf415 @Vaishali Agarwal last edited by

                                    @Vaishali-Agarwal
                                    you mean ?
                                    'env' => env('APP_ENV', 'production'),

                                    1 Reply Last reply Reply Quote 0
                                    • V
                                      Vaishali Agarwal last edited by

                                      @raouf415
                                      Yes, if inside .env the APP_DEBUG=false it means the application is under production mode else if APP_DEBUG=true (development mode)

                                      R 1 Reply Last reply Reply Quote 0
                                      • R
                                        raouf415 @Vaishali Agarwal last edited by

                                        @Vaishali-Agarwal App_debug = true

                                        1 Reply Last reply Reply Quote 0
                                        • V
                                          Vaishali Agarwal last edited by Vaishali Agarwal

                                          @raouf415
                                          kindly execute the below command inside velocity package

                                          npm i
                                          
                                          npm run prod
                                          
                                          R 1 Reply Last reply Reply Quote 0
                                          • R
                                            raouf415 @Vaishali Agarwal last edited by

                                            @Vaishali-Agarwal
                                            node_modules deleted
                                            Npm i it's ok
                                            npm run prod
                                            prod /home/raouf/ecommerce/new/ecommerce/vendor/bagisto/bagisto/packages/Webkul/Velocity

                                            npm run production

                                            @ production /home/raouf/ecommerce/new/ecommerce/vendor/bagisto/bagisto/packages/Webkul/Velocity
                                            cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

                                            /home/raouf/ecommerce/new/ecommerce/vendor/bagisto/bagisto/packages/Webkul/Velocity/node_modules/webpack-cli/bin/cli.js:281
                                            throw err;
                                            ^

                                            ValidationError: Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.

                                            • configuration.module.rules[11] should be one of these:
                                              ["..." | object { compiler?, dependency?, descriptionData?, enforce?, exclude?, generator?, include?, issuer?, loader?, mimetype?, oneOf?, options?, parser?, realResource?, resolve?, resource?, resourceFragment?, resourceQuery?, rules?, sideEffects?, test?, type?, use? }, ...]
                                              -> A rule.
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post