Skip to content

Latest commit

 

History

History
133 lines (85 loc) · 7.88 KB

Development Tools.md

File metadata and controls

133 lines (85 loc) · 7.88 KB

Development Tools

  • You understand what webpack is used for and what problem it solves 📚
  • You understand what webpack plugins are and you can add and configure when needed 📚
  • You understand the key concepts: entry, output, loaders and plugins
  • You know how to pass environmental variables to the application
  • You know how to configure a webpack from scratch to generate a project's build
  • You can configure a build process using Rollup's API
  • You know the key concepts: input, output, targets and plugins
  • You can add needed plugins and are able to configure them
  • You're able to use inline commands to add, install & remove packages 📚
  • You understand the benefits of yarn.lock file 📚
  • You know how to run package.json scripts 📚
  • You can upgrade packages using upgrade-interactive command
  • You know how to initialize and publish a new package
  • You're able to use inline commands to add, install & remove packages 📚
  • You understand the benefits of package-lock.json file 📚
  • You know how to run package.json scripts 📚
  • You can upgrade packages to newer versions
  • You know how to define new package.json scripts
  • You know how to initialize and publish a new package
  • You can generate a new app using create-react-app cli 📚
  • You can create and publish your own CRA template
  • You can create components using plop command line tool 📚
  • You can create and update current templates
  • You can prototype your components using storybooks
  • You can install and configure storybooks in your project
  • You can connect theme to your storybooks
  • You can use routing-aware components with the help of storybook-react-router 📚
  • You know how to describe component's prop types
  • You know how to define object shapes
  • You use redux-devtools to see the current state and play with the state change history 📚
  • You can create and configure redux-devtools so your store is available to be inspected
  • You're able to install and configure react-hot-loader to refresh the build when component changes
  • You can run eslint and fix the warnings and errors 📚
  • You can add or exclude rules
  • You can run prettier and auto-correct errors 📚
  • You can add or exclude rules
  • You know how to configure stylelint in within the project's build tools
  • You know how to add a set o rules, exclude exceptions and add rules according to project needs
  • You know how to inject env variables via dotenv and use them when needed
  • You know when to commit env files to the repository and when not to

Contribution

We are very open to contributions to extend or change the requirements based on your gut and experience. To contribute you can use a pull request which will be later validated by our technical team and added to the main docs.

If you will spot any issues please add them in the Issues section.

Credits

This page is maintained by the 🔹 Flairs.ai and 🇵🇱 Apptension teams.

If you would like to create a dedicated Developer Handbook for your company, you can e-mail us 👉 contact@flairs.ai

License

MIT License

© 2020 Flairs Sp. z o.o.

Built and maintained by Flairs and Apptension.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.