You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Install all the required dependecies after cloning or downloading the repository using Node v18 or higher:
npm run install
Run the dev server:
npm run dev
To compile and minify a demo instance:
npm run build
To preview the compiled production files :
npm run preview
To compile and minify a demo instance as a web component library:
npm run build -- --lib
Folder Structure
.
├── core # CLI & Client source code
├── docs # Documentation files
├── templates # Base configurations and eodash templates
├── tests # CLI & Client component tests folder
├── widgets # Vue components as internal widgets.
├── public # Statically served directory
└── README.md
Writing commits
To ensure clear communication with the package consumers and enable machine-readable commits, we adhere to The Conventional Commits specification that allows the generation of semVer releases and associated change logs using googleapis/release-please.
The most important prefixes you should have in mind are:
fix: which represents bug fixes, and correlates to a SemVer patch.
feat: which represents a new feature, and correlates to a SemVer minor.
feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.