Skip to content
The javascript metaframework
Branch: master
Clone or download
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 Removes duplicate README Jul 2, 2018
examples Update README.md Apr 1, 2019
spec Adding history state to popstate event for pushState and replaceState Apr 11, 2019
src Not allowing triggerAppChange to pass in pendingPromises or Apr 22, 2019
.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
.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
CONTRIBUTING.md Updates link to contributing docs Jun 28, 2018
LICENSE license and readme Sep 23, 2015
README.md Removing saucelabs badge from readme Apr 11, 2019
jest.config.json
package.json v4.3.2 Apr 16, 2019
rollup.config.js Also bundling to System.register format, for script tagging. Mar 28, 2019
yarn.lock Try to unmount an appOrParcel when mount fails Mar 26, 2019

README.md

npm version Build Status

single-spa

Join the chat on Slack

A javascript metaframework

Build micro frontends that coexist and can each 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

A live demo is available and the source code for that demo is available in the single-spa-examples repository.

Also, you can check out a simple webpack starter project which is simpler and hopefully easier to get started with.

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.

Project roadmap

We're trying out github's Projects feature (here) and are keeping it up-to-date with the fancy things in the works for single-spa.

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.