composer update "vendor/*"
composer update vendor/package vendor/package2
composer update vendor/package
composer.lock
composer update
1. The composer.lock file will be ignored
2. composer.json
file dependencies will be installed and updated (if a dependency is not installed it will be downloaded)install
command reads the composer.json
file from the current directory, resolves the dependencies, and installs them into vendor
composer install / composer i
If composer.lock
file exists, installs exactly what's specified in this file
Otherwise
1. Reads composer.json
file to look out what dependencies needs to be installed
2. Writes the composer.lock with the information of the project (installed dependencies)composer.json
composer init
npm install -g live-server
After installing, the package should be started by running the command in consolelive-server
npm install -g browserify
If our app main JS file is app.js, then running the command will create one bundle.js
filebrowserify app.js > bundle.js
live-server
did not work
browserify
did not work
The problem solved after running this command in Windows PowerShell
(open as an administrator)Set-ExecutionPolicy -Scope "CurrentUser" -ExecutionPolicy "Unrestricted"