pon-shared-pon.universe.frontend.shared.componentlibrary v1.0.0
Prerequisites
! It is expected that you open the Bash terminal in the root of the project. e.g. In Visual Studio Code the terminal is opened with shortcut ctrl + ~
e.g. D:\web\Pon.Universe\Frontend.Shared.ComponentLibrary
Install NVM and restart your computer.
- Windows: https://github.com/coreybutler/nvm-windows/releases. Download 'nvm-setup.zip'.
- Linux: See 'Installation' section of Node Version Manager.
Use NVM to install and set the correct version of Node.js. This should be the LTS version.
Windows:
- Get
[version]by checking the content of the.nvmrcfile for the correct Node.js version. - Install that Node.js version by executing
$ nvm install [version] - Set the correct NVM version by executing
$ nvm use [version]
! Nvm for windows it is not possible to automatically read the
.nvmrcfile to set the correct version. So manually use the version of the.nvmrc.Linux:
- Run
nvm useto set the correct version of Node.js.
- Get
Installation
! It is expected that you open the Bash terminal in the root of the project. e.g. In Visual Studio Code the terminal is opened with shortcut ctrl + ~
e.g. D:\web\Pon.Universe\Frontend.Shared.ComponentLibrary
node -v
- Install the NPM packages by running the following command:
npm install- Link local packages together and install remaining package dependencies
lerna bootstrapCommands
Publishes the components to the valtech nexus server: https://nexus.valtech.nl/repository/Pon.Universe.Frontend.Shared/
npm run publishThis command will first check the current git branch and state. Publishing is only allowed from the develop branch and the branch must be up-to-date with no uncommited changes. If those criteria are not met, the command will throw an exception and the publication will not continue.
Lints and fixes files
npm run lintRun your unit tests
npm run test:unitMore information on creating / deleting packages and adding dependencies to packages:
https://efocus.atlassian.net/wiki/spaces/PONUNI/pages/1237975718/Front-end+Shared+Component+Library
Troubleshooting
Windows:
'npm' is not recognized as an internal or external commandFix: Update to the latest nvm version and reinstall the used node version.
Version 1.1.6 of NVM is incompatible with the later downloads of node and causes an error when installing NPM.
Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 8.xFix: npm rebuild node-sass
Tools
For real-time code analysis & formatting in Visual Studio Code:
- Install a EditorConfig plugin for your prefered IDE.
- Visual Studio Code: e.g.
EditorConfig for VS Code
- Visual Studio Code: e.g.
Install a PrettierEditor plugin for your prefered IDE.
- Visual Studio Code: e.g.
Prettier - Code formatter
! Make sure that you point your Editor to the .prettierignore in the root of the project.
! e.g. Visual Studio Code: If you open the editor in the root of the project
Pon.Universe/Automotive.Cluster.Common.CarSalesToolyou don't need to change anything.- Visual Studio Code: e.g.
Install a ESLint plugin for your prefered IDE.
- Visual Studio Code: e.g.
ESLint
- Visual Studio Code: e.g.
- Install a Vue plugin for your prefered IDE.
- Visual Studio Code: e.g.
Vetur
- Visual Studio Code: e.g.
For real-time code analysis & formatting in the browser:
- Install
Vue devtoolsfor the browser- Chrome: Vue.js devtools
- Firefox: Vue.js devtools
Visual Studio Code Settings
How to open the settings.json see here
"editor.formatOnSave": true,
"eslint.autoFixOnSave": true,
"eslint.validate": [
"javascript",
"javascriptreact",
{
"language": "vue",
"autoFix": true
}
],7 years ago