https://github.com/moxb/moxb

Typescript framework for architecting large scale web application.
https://github.com/moxb/moxb

framework javascript mobx moxb reactive-programming reactjs typescript

Last synced: 10 months ago
JSON representation

Typescript framework for architecting large scale web application.

• Host: GitHub
• URL: https://github.com/moxb/moxb
• Owner: moxb
• License: mit
• Created: 2018-07-13T10:04:06.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2023-03-02T03:30:26.000Z (about 3 years ago)
• Last Synced: 2025-06-01T12:11:14.755Z (10 months ago)
• Topics: framework, javascript, mobx, moxb, reactive-programming, reactjs, typescript
• Language: TypeScript
• Homepage: http://www.moxb.org
• Size: 10.9 MB
• Stars: 7
• Watchers: 3
• Forks: 1
• Open Issues: 42
• Metadata Files:
  • Readme: README.md
  • Changelog: ChangeLog.md
  • License: LICENSE

Awesome Lists containing this project

README

          
[![moxb Logo](https://dl.dropboxusercontent.com/s/6w24mniyvlvij0s/moxb_logo_github.png?dl=0)](http://moxb.org/)

  moxb is a modular, opinionated [Typescript](http://www.typescriptlang.org/) framework for architecting large scale web application with [React](https://reactjs.org/) and [mobx](https://mobx.js.org/).

  moxb [/(mox) (b)/] stands for **mox** [latin for *just*] and **b** [*binding*] which describes the core of the framework. It creates loosely coupled binding between different frameworks or libraries with a set of different architectural patterns, to create lean modern web applications.

see [ChangeLog](./ChangeLog.md)

### How to ship a new version

- Create a release in the [ChangeLog](./ChangeLog.md) file

- in the top level `package.json` update the version (it's not done by lerna)

  - make sure that `package-lock.json` is up to date

- call `make`

- commit all changes

- push all changes (don't create the git tag, lerna will do it automatically)

- `. ./admin/activate`

- `lerna publish`

  - choose the proper release version (minor, major, breaking).

- Only the changed packages will be published

- However the version number always be incremented to the proper latest one

If `lerna publish` doesn't want to release use the `--force-publish` option.