Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

React Tutorial is the best place to learn how to use React and Meteor together

NotificationsYou must be signed in to change notification settings

meteor/react-tutorial

Repository files navigation

If you are looking for the tutorial, please go tohttps://react-tutorial.meteor.com and check it there.

This repository is the place to check the code (src folder) and to make contributions.

Read in the tutorial home page where you should ask questions (spoiler:Forums orSlack).

This is ahexo static site used to generate theMeteor React Tutorial Docs.

Contributing

We'd love your contributions! Please send us Pull Requests or open issues ongithub. Also, read thecontribution guidelines.

If you are making a larger contribution, you may need to run the site locally:

Running locally

  • Installnvm to manage your Node.js (yes, this is an hexo project and not Meteor, in Meteor you don't need to worry about Node.js versions at all)

    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash

  • Install Node.js 8.11.2:

    nvm install 8.11.2

  • Install the project

    npm install

  • Run it

    npm start

Styles and Lint

Make sure your changes are not breaking styles and lint rules, in the root project, run:

  • npm install
  • npm run quave-check

quave-check should not return any error or warning. If it does you need to fix them before sending a PR.

If you get an error because some npm modules are not resolved (import/no-unresolved) you need to runnpm install inside the Meteor project that is throwing this error so you generate thenode_modules folder for it.

We have a git hook to prevent commits that are not passing these rules but it's good to double-check as maybe your hooks set up can be messed up.

Making a Pull Request

  • Create a fork and make your changes on it.

  • Test your changes and make sure you sync your code changes (src folder) with your text changes (tutorial folder).

  • Build your changes:

npm run build

  • Create your Pull Request againstmaster branch.

  • Sign the CLA.

  • Wait for feedback or approval.


[8]ページ先頭

©2009-2025 Movatter.jp