We appreciate any community contributions to this project, whether in the form of issues or pull requests.
This document outlines what we'd like you to follow in terms of commit messages and code style.
It also explains what to do in case you want to setup the project locally and run tests.
Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub
This project is written in ES2015 and transpiled to ES5 using Babel, to the dist directory. This should generally only happen at publishing time, or for testing purposes only.
Run npm install to install all necessary dependencies. When running npm install locally, dist is not compiled.
All necessary dependencies are installed under node_modules and any necessary tools can be accessed via npm scripts. There is no need to install anything globally.
When importing local, in develoment code, via index.js, this file checks if dist exists and uses that. Otherwise, it uses the code from lib.
If you have a dist directory, run npm run clean.
Axios, one of the main dependencies is vendored. This generally shouldn't matter, but if you'd like to understand why, check SETUP.md
npm run cleanremoves any built filesnpm run buildbuilds vendored files, node package and browser versionnpm run build:distbuilds ES5 sources from ES6 onesnpm run build:standalonebuilds unminified and minified sources for browsers
This project has unit and integration tests. Both of these run on both Node.js and Browser environments.
Both of these test environments are setup to deal with Babel and code transpiling, so there's no need to worry about that
npm testruns all three kinds of tests and generates a coverage reportnpm run test:onlyruns Node.js unit tests without coverage.npm run test:coverto run Node.js unit tests with coverage.npm run test:debugruns babel-node in debug mode (same as runningnode debug).npm run test:integrationruns the integration tests against the Contentful CDA APInpm run test:browser-localruns both the unit and integration tests using Karma against local browsers.npm run test:ciruns tests in CInpm run test:browser-remoteruns both the unit and integration tests using Karma against Sauce Labs. This is only usable in the CI environment, as it expects the credentials and connection tunnel to be present.
Code is documented using JSDoc 3, and reference documentation is published automatically with each new version.
npm run docs:watchwatches code directory, and rebuilds documentation when anything changes. Useful for documentation writing and development.npm run docs:devbuilds code and builds docs afterwards. Used bynpm run docs:watch. Code building is required as the documentation is generated from the unminified ES5 compiled sources, rather than the original ES6 sources. You should then open the generatedout/contentful/index.htmlin your browser.npm run docs:buildbuilds documentation.npm run docs:publishbuilds documentation and publishes it to github pages.
This project uses standard. Install a relevant editor plugin if you'd like.
Everywhere where it isn't applicable, follow a style similar to the existing code.
This project uses the Angular JS Commit Message Conventions, via semantic-release. See the semantic-release Default Commit Message Format section for more details.
This project strictly follows Semantic Versioning by use of semantic-release.
This means that new versions are released automatically as fixes, features or breaking changes are released.
You can check the changelog on the releases page.