Skip to content

Latest commit

 

History

History
232 lines (160 loc) · 8.54 KB

CONTRIBUTING.md

File metadata and controls

232 lines (160 loc) · 8.54 KB
Raw

Contribute to Strapi

First off, thanks for taking the time to contribute! 🎉👍

The following is a set of guidelines for contributing to Strapi and its packages.

Strapi is an open-source project administered by the Strapi team.

Before contributing, ensure that your effort is aligned with the project's roadmap by talking to the maintainers, especially if you are going to spend a lot of time on it. Feel free to join us on Slack if you are interested in helping us or drop us an email if you are interested in working with us.

Code of Conduct

This project and everyone participating in it is governed by the Strapi Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].

Open Development & Community Driven

Strapi is open-source under the MIT license. All the work done is available on GitHub. The core team and the contributors send pull requests which go through the same validation process.

Every user can send a feature request using the issues on GitHub. Feel free to upvote 👍 existing feature request

Repository Organization

We made the choice to use a monorepo design such as React, Babel, Meteor or Ember do. It allows the community to easily maintain the whole ecosystem up-to-date and consistent.

The Babel team wrote an excellent short post about the pros and cons of the monorepo design.

We will do our best to keep the master branch as clean as possible, with tests passing all the times. However, it can happen that the master branch moves faster than the release cycle. To ensure you have the latest stable version, please refer to the release on npm.

If you send a pull request, please do it against the master branch. We are developing upcoming versions separately to ensure non-breaking changes from master to the latest stable major version.

Setup Development Environment

To facilitate the contribution, we drastically reduce the amount of commands necessary to install the entire development environment. First of all, you need to check if you're using the required versions of Node.js and npm

Note: Fish shell users - due to the way fish shell deals with symlinks, the following steps will not work.

Then, please follow the instructions below:

1. ▪️ Fork the repository

Go to the repository and fork it to your own GitHub account.

2. 💿 Clone from your repository

git clone [email protected]:YOUR_USERNAME/strapi.git

3. ⏳ Installation

Go to the root of the repository.

cd strapi

Two setup are available... with or without the front-end builds.

Without the front-end builds, you won't be able to access the administration panel via http://localhost:1337/admin. You'll have to run the administration separately and access it through http://localhost:4000/admin.


Without the front-end builds (recommended)

npm run setup

or with the front-end builds

npm run setup:build

⚠️  If the installation failed, please remove the global packages related to Strapi. The command npm ls strapi will help you to find where your packages are installed globally.

4. 🏗 Create a new project

You can open a new terminal window and go into any folder you want for the next steps.

cd ../workspace/

The command to generate a project is the same, except you have to add the --dev argument at the end of line.

strapi new my-project --dev

5. 🚀 Start the project

First, you have to start the server.

cd ./my-project
strapi start

The server (API) is available at http://localhost:1337

⚠️  If you've followed the recommended setup, you should not be able to reach the administration panel at http://localhost:1337/admin.

Then, you have to start the Webpack server to build and run the administration.

cd ./my-project/admin
npm run start

The administration panel is available at http://localhost:4000/admin

Awesome! You are now able to contribute to Strapi.

Plugin Development Setup

To create a new plugin, you'll have to run the following commands:

1. 🏗 Generate a new plugin

cd ./my-project
strapi generate:plugin my-plugin

2. ✅ Verify the symlink

Make you that the strapi-helper-plugin is linked to your project.

Please run this command in the repository folder where Strapi is cloned:

cd /repository/strapi/packages/strapi-helper-plugin
npm link

Link the strapi-helper-plugin node_modules in the plugin folder:

cd ./my-project/plugins/my-plugin
npm link strapi-helper-plugin

3. 🚀 Start the project

cd ./my-project/admin
npm run start

The administration panel is available at http://localhost:4000/admin

Running the tests

You can run three different kind of tests:

  • Unit tests
  • End to end tests
  • Cypress (integration) tests

Unit tests

This will run the npm test script in every packages

$ npm run test:unit

End to end

This will create a test app, start it and run the end to end tests against it.

️️️️️️️You can change test/e2e.js to configure the database you want to use:

// test/e2e.js
//...
const main = async () => {
  // you can switch databases.mongo for databases.mysql or any other
  const database = process.argv.length > 2 ? process.argv.slice(2).join(' ') : databases.mongo;
  //...
}

Then run

$ node test/e2e.js

Cypress

This will create a test app, start it and finally run the cypress tests against it.

You can change test/createTestApp.js to configure the database you want to use.

// test/createTestApp.js
//...
const main = async () => {
  // you can switch databases.mongo for databases.mysql or any other
  const database = process.argv.length > 2 ? process.argv.slice(2).join(' ') : databases.postgres;
  //...
}

⚠️ To run the cypress test you must have run npm run setup:build to setup the repository

Then run

# generate the test app
$ node test/createTestApp.js
# run the testApp in the background (️️️⚠️ be carefull to kill the process after the tests have run)
$ node test/startTestApp.js & 
# run cypress
$ node test/cypress

Reporting an issue

Before reporting an issue you need to make sure:

  • You are experiencing a concrete technical issue with Strapi (ideas and feature proposals should happen on Slack).
  • You are not asking a question about how to use Strapi or about whether or not Strapi has a certain feature. For general help using Strapi, please refer to the official Strapi documentation. For additional help, ask a question on StackOverflow.
  • You have already searched for related issues, and found none open (if you found a related closed issue, please link to it in your post).
  • Your issue title is concise, on-topic and polite.
  • You can provide steps to reproduce this issue that others can follow.
  • You have tried all the following (if relevant) and your issue remains:
    • Make sure you have the right application started.
    • Make sure you've killed the Strapi server with CTRL+C and started it again.
    • Make sure you closed any open browser tabs pointed at localhost before starting Strapi.
    • Make sure you do not have any other Strapi applications running in other terminal windows.
    • Make sure the application you are using to reproduce the issue has a clean node_modules directory, meaning:
      • no dependencies are linked (e.g. you haven't run npm link)
      • that you haven't made any inline changes to files in the node_modules folder
      • that you don't have any weird global dependency loops. The easiest way to double-check any of the above, if you aren't sure, is to run: $ rm -rf node_modules && npm cache clear && npm install.