https://github.com/opencomponents/oc

OpenComponents, serverless in the front-end world for painless micro-frontends delivery
https://github.com/opencomponents/oc

components continuous-delivery microfrontends opencomponents serverless ui-composition

Last synced: about 2 months ago
JSON representation

OpenComponents, serverless in the front-end world for painless micro-frontends delivery

• Host: GitHub
• URL: https://github.com/opencomponents/oc
• Owner: opencomponents
• License: mit
• Created: 2015-01-20T23:56:08.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2024-04-11T07:06:23.000Z (8 months ago)
• Last Synced: 2024-04-14T07:49:32.471Z (8 months ago)
• Topics: components, continuous-delivery, microfrontends, opencomponents, serverless, ui-composition
• Language: JavaScript
• Homepage: https://opencomponents.github.io/
• Size: 7.29 MB
• Stars: 1,392
• Watchers: 63
• Forks: 122
• Open Issues: 24
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-micro-frontends - oc
• awesome-micro-frontends - OpenComponents
• awesome-micro-frontends - OpenComponents, a framework for developing and distributing html components

README

        
# ![oc](https://raw.githubusercontent.com/opencomponents/oc/master/logo-type.png)

OpenComponents, **serverless in the front-end world**.

OpenComponents is an open-source framework that allows fast-moving teams to easily build and deploy front-end components. It abstracts away complicated infrastructure and leaves developers with very simple, but powerful building blocks that handle scale transparently.

#### How does it work?

First, **you create your component**. It can contain logic to get some data (using node.js) and then the view, including css and js. It can be what you want, including _React_ or _Angular_ components or whatever you like.

Then, **you publish it** to the OpenComponents registry and you wait a couple of seconds while the registry prepares your stuff to be production-ready.

Now, every web app in your private or public network can **consume the component** via its own HTTP endpoint during server-side rendering or just in the browser.

We have been using it for more than two years in production at OpenTable, for shared components, third party widgets, e-mails and more. [Learn more about OC](http://tech.opentable.co.uk/blog/2016/04/27/opencomponents-microservices-in-the-front-end-world/).

[![npm version](https://img.shields.io/npm/v/oc.svg)](https://npmjs.org/package/oc)

[![node version](https://img.shields.io/node/v/oc.svg)](https://npmjs.org/package/oc)

[![Known Vulnerabilities](https://snyk.io/test/github/opencomponents/oc/badge.svg)](https://snyk.io/test/github/opencomponents/oc)

[![downloads](https://img.shields.io/npm/dm/oc.svg?label=downloads+from+npm)](https://npmjs.org/package/oc)

[![Join the chat at https://gitter.im/opentable/oc](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/opentable/oc?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

## Links

- [Website](https://opencomponents.github.io)

- [Documentation](https://opencomponents.github.io/docs/intro)

- [Requirements and build status](#requirements-and-build-status)

- [Changelog](CHANGELOG.md)

- [Awesome resources about OC](https://github.com/matteofigus/awesome-oc)

- [Contributing guidelines](CONTRIBUTING.md)

- [Code of conduct](CONTRIBUTING.md#code-of-conduct)

- [Troubleshooting](CONTRIBUTING.md#troubleshooting)

- [Gitter chat](https://gitter.im/opentable/oc)

## Requirements and build status

Disclaimer: This project is still under heavy development and the API is likely to change at any time. In case you would find any issues, check the [troubleshooting page](CONTRIBUTING.md#troubleshooting).

## License

MIT