valitydev/fe-core
14
0
Fork 0
mirror of https://github.com/valitydev/fe-core.git synced 2024-11-06 02:25:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Frontend Libs Monorepo
23 Commits 1 Branch 44 Tags 342 KiB
TypeScript 66.2%
JavaScript 33.4%
Shell 0.4%
master
Go to file
Pavel Popov ca81289b22
Let's make it opensource (#20)
2021-08-13 18:37:50 +03:00
.github/workflows FRONTEND-542: Add prepared rules (#16) 2021-04-28 15:26:23 +03:00
.husky FRONTEND-509: Try to allow GitHub Actions to push master (#10) 2021-04-15 15:33:13 +03:00
packages FRONTEND-604: Id generator repair (#19) 2021-06-07 15:01:38 +03:00
.commitlintrc.json FRONTEND-509: Configure CommitLint, Add Partial-Fetcher & Component Changes Util (#2) 2021-04-13 15:31:05 +03:00
.eslintrc.js FRONTEND-509: Configure CommitLint, Add Partial-Fetcher & Component Changes Util (#2) 2021-04-13 15:31:05 +03:00
.gitignore FRONTEND-233: Init eslint plugin (#11) 2021-04-26 16:14:06 +03:00
.npmrc FRONTEND-509: Select progress util (#9) 2021-04-15 13:43:34 +03:00
.prettierignore init 2021-04-12 12:00:30 +03:00
.prettierrc init 2021-04-12 12:00:30 +03:00
lerna.json FRONTEND-509: Select progress util (#9) 2021-04-15 13:43:34 +03:00
LICENSE Let's make it opensource (#20) 2021-08-13 18:37:50 +03:00
package-lock.json FRONTEND-604: Id generator repair (#19) 2021-06-07 15:01:38 +03:00
package.json FRONTEND-509: Try to allow GitHub Actions to push master (#10) 2021-04-15 15:33:13 +03:00
README.md FRONTEND-509: Select progress util (#9) 2021-04-15 13:43:34 +03:00
tsconfig.json FRONTEND-509: Configure CommitLint, Add Partial-Fetcher & Component Changes Util (#2) 2021-04-13 15:31:05 +03:00

README.md

Frontend Libs Monorepo

Installation

  1. Add .npmrc file into your project root directory

    @rbkmoney:registry=https://npm.pkg.github.com/

  2. Authenticate to GitHub Packages

  3. Install

    npm i '@rbkmoney/<PACKAGE_NAME>'

Contributing

Installation

npx lerna bootstrap

Deps management

  • Add 
    lerna add <package>[@version] [--dev] [--exact] [--peer]

Versioning & GIT Commits

ConventionalCommits

  • fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).
  • feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).
  • BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
  • types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.
  • footers other than BREAKING CHANGE: may be provided and follow a convention similar to git trailer format.

Development

Linking to the project that needs

npm link '<PATH>/fe-core/packages/<PACKAGE_DIR>'

# Example:
# npm link '../fe-core/packages/utils'

Publish

is now performed automatically on CI

  1. Bump prerelease every time you push 
    npm run versionup
  2. Bump release & publish before merge into master 
    npm run release-versionup
npm run release-publish