GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - caplin/caplin-dev-tools

BranchesTags
Open more actions menu

Latest commit

 

History

1,265 Commits
1,265 Commits

Folders and files

NameName
Last commit message
Last commit date
aliases-plugin
aliases-plugin
 
 
brjs-app-converter
brjs-app-converter
 
 
build-tasks
build-tasks
 
 
caplin-versioning
caplin-versioning
 
 
cli
cli
 
 
express-dev-server
express-dev-server
 
 
html-loader
html-loader
 
 
i18n-loader
i18n-loader
 
 
jasmine-karma-test-runner
jasmine-karma-test-runner
 
 
jstestdriver-functions
jstestdriver-functions
 
 
karma-jstd-adapter
karma-jstd-adapter
 
 
karma-jstd
karma-jstd
 
 
karma-log-update-reporter
karma-log-update-reporter
 
 
karma-test-runner
karma-test-runner
 
 
module-source-converter
module-source-converter
 
 
node-logger
node-logger
 
 
patch-loader
patch-loader
 
 
webpack-config-app
webpack-config-app
 
 
xml-loader
xml-loader
 
 
.eslintrc.js
.eslintrc.js
 
 
.gitignore
.gitignore
 
 
.travis.yml
.travis.yml
 
 
README.md
README.md
 
 
package.json
package.json
 
 
release-package.js
release-package.js
 
 

Repository files navigation

THIS REPO HAS NOW BEEN MERGED INTO THE CAPLIN FRONT END MONOREPO; IT IS NO LONGER BEING ACTIVELY USED

For developing Caplin applications using node.js tooling

This monorepo contains packages that are designed to be used as part of a Caplin development environment. They are not designed for usage in generic web applications. The more important packages have their own README.md files.

Releasing packages

We are using conventional-changelog to programatically create changelogs.

Releasing a new version of a package

Verify the package already has a CHANGELOG.md, if not see below for steps to create one.

  1. Make changes
  2. Commit those changes following the conventional-changelog commit style
  3. yarn run release

Creation of a CHANGELOG.md

If the package you are modifying has no CHANGELOG.md file, then create a CHANGELOG.md. First cd into the package folder and run:

conventional-changelog -p angular -i CHANGELOG.md -s -r 0 --commit-path .

You should run this before you make your commits and update the package.json version.

Then tag the package's last release (the last time its version was updated).

git tag [email protected] 50100c3aa8376e

The format of the tag is NAME_OF_PACKAGE@LAST_PUBLISHED_VERSION and the commit is the commit where the package.json version was changed.

Push the newly created tag to the server

git push origin [email protected]

About

No description, website, or topics provided.

Resources

Readme
Activity
Custom properties

Stars

9 stars

Watchers

20 watching

Forks

2 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.