Skip to content
OpenComponents, serverless in the front-end world for painless micro-frontends delivery
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add github issue/PR templates Nov 29, 2017
src 0.47.0 Apr 30, 2019
tasks oc package now is able to reuse modules in component path Nov 30, 2018
test update to only set headers if 1 component requested Apr 29, 2019
.editorconfig Added editorconfig file Nov 9, 2018
.eslintignore remove head.js Jun 20, 2017
.eslintrc.json reverting 5d32c0a Aug 12, 2017
.gitignore Added acceptance test Mar 28, 2018
.npmignore Merge branch 'master' into cleanup Jul 13, 2017
.nvmrc
.travis.yml
CHANGELOG.md
CONTRIBUTING.md Rename publish tasks Jan 31, 2018
LICENSE Remove support for node 6 Mar 25, 2019
README.md Remove support for node 6 Mar 25, 2019
appveyor.yml Remove support for node 6 Mar 25, 2019
dependencies.yml Greenkeeper => Dependencies.io May 31, 2018
logo-type.png loto-type leftover Jan 30, 2018
logo.png updated logo asset Jan 26, 2018
package.json Merge pull request #1033 from opencomponents/deps/update-7e845052 May 15, 2019

README.md

oc

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.

npm version node version Dependency Status Known Vulnerabilities downloads Join the chat at https://gitter.im/opentable/oc

Links

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.

linux build

Node 8 Node 9 Node 10
Node8 Node9 Node10

windows build

License

MIT

You can’t perform that action at this time.