Skip to content
Microfrontends made easy
JavaScript
Branch: master
Clone or download
frehner and joeldenning outputting dev builds for all formats. (#347)
currently don't do much besides not terser-ify the file, but maybe there's more in the future?
Latest commit 81948fb Sep 7, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update issue templates (#240) Oct 16, 2018
docs
examples Update README.md Apr 1, 2019
spec Change LOAD_ERROR retry to be throttled via timestamp (#345) Sep 5, 2019
src Change LOAD_ERROR retry to be throttled via timestamp (#345) Sep 5, 2019
typings
.babelrc Merge branch 'master' into rollup Feb 9, 2019
.eslintrc 3.7.0 (#153) Jan 11, 2018
.gitignore Triggering another travis test run Apr 16, 2018
.npmignore Rewrite for 2.0 Apr 18, 2016
.travis.yml using jest as the test runner (#274) Feb 9, 2019
CHANGELOG.md Adding CHANGELOG.md that points to github releases page. Jul 9, 2018
CODE_OF_CONDUCT.md Typo Jun 28, 2018
CONTRIBUTING.md Updates link to contributing docs Jun 28, 2018
LICENSE license and readme Sep 23, 2015
README.md
jest.config.json Moving unregisterApplication to dev tools exposed methods. May 2, 2019
package.json outputting dev builds for all formats. (#347) Sep 7, 2019
rollup.config.js outputting dev builds for all formats. (#347) Sep 7, 2019
yarn.lock Upgrading dependencies to remove security warning (#344) Sep 4, 2019

README.md

npm version Build Status

single-spa

Join the chat on Slack

Donate to this project

A javascript framework for front-end microservices

Build micro frontends that coexist and can (but don't need to) be written with their own framework. This allows you to:

Documentation

You can find the single-spa documentation on the website.

Check out the Getting Started page for a quick overview.

Demo and examples

Please see the examples page on the website.

Want to help?

Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing on the single-spa website.

Contributing

The main purpose of this repository is to continue to evolve single-spa, making it better and easier to use. Development of single-spa, and the single-spa ecosystem happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving single-spa.

Code of Conduct

Single-spa has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.

Contributing Guide

Read our contributing guide to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to single-spa.

You can’t perform that action at this time.