Alternatives to React Starter Kit logo

Alternatives to React Starter Kit

React, Create React App, React.js Boilerplate, React Router, and styled-components are the most popular alternatives and competitors to React Starter Kit.
71
86
+ 1
8

What is React Starter Kit and what are its top alternatives?

React Starter Kit is an opinionated boilerplate for web development built on top of Facebook's React library, Node.js / Express server and Flux architecture. Containing modern web development tools such as Webpack, Babel and BrowserSync.
React Starter Kit is a tool in the JavaScript Framework Components category of a tech stack.
React Starter Kit is an open source tool with 21.2K GitHub stars and 4.1K GitHub forks. Here鈥檚 a link to React Starter Kit's open source repository on GitHub

Top Alternatives to React Starter Kit

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • Create React App
    Create React App

    Create React apps with no build configuration.

  • React.js Boilerplate
    React.js Boilerplate

    Quick setup for new performance orientated, offline鈥揻irst React.js applications featuring Redux, hot鈥搑eloading, PostCSS, react-router, ServiceWorker, AppCache, FontFaceObserver and Mocha. ...

  • React Router
    React Router

    React Router is a complete routing solution designed specifically for React.js. It painlessly synchronizes the components of your application with the URL, with first-class support for nesting, transitions, and server side rendering. ...

  • styled-components
    styled-components

    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 馃拝 ...

  • Storybook
    Storybook

    It is an open source tool for developing UI components in isolation for React, Vue, and Angular. It makes building stunning UIs organized and efficient. ...

  • Ant Design
    Ant Design

    An enterprise-class UI design language and React-based implementation. Graceful UI components out of the box, base on React Component. A npm + webpack + babel + dora + dva development framework. ...

  • Angular CLI
    Angular CLI

    A command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications. You can use the tool directly in a command shell, or indirectly through an interactive UI such as Angular Console. ...

React Starter Kit alternatives & related posts

React logo

React

128.4K
104.7K
3.8K
A JavaScript library for building user interfaces
128.4K
104.7K
+ 1
3.8K
PROS OF REACT
  • 774
    Components
  • 657
    Virtual dom
  • 567
    Performance
  • 491
    Simplicity
  • 438
    Composable
  • 176
    Data flow
  • 162
    Declarative
  • 124
    Isn't an mvc framework
  • 114
    Reactive updates
  • 111
    Explicit app state
  • 39
    JSX
  • 23
    Learn once, write everywhere
  • 19
    Uni-directional data flow
  • 17
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 10
    Great perfomance
  • 8
    Built by Facebook
  • 7
    Javascript
  • 5
    Speed
  • 5
    TypeScript support
  • 4
    Feels like the 90s
  • 4
    Hooks
  • 4
    Awesome
  • 4
    Scalable
  • 4
    Easy to start
  • 3
    Server Side Rendering
  • 3
    Fancy third party tools
  • 3
    Props
  • 3
    Obama
  • 3
    Server side views
  • 3
    Functional
  • 3
    Scales super well
  • 3
    Excellent Documentation
  • 3
    Cross-platform
  • 2
    Rich ecosystem
  • 2
    Start simple
  • 2
    Allows creating single page applications
  • 2
    Sdfsdfsdf
  • 2
    Beautiful and Neat Component Management
  • 2
    Very gentle learning curve
  • 2
    Has functional components
  • 2
    Simple
  • 2
    Closer to standard JavaScript and HTML than others
  • 2
    Super easy
  • 2
    Has arrow functions
  • 2
    Strong Community
  • 2
    Great migration pathway for older systems
  • 2
    SSR
  • 2
    Fast evolving
  • 2
    Simple, easy to reason about and makes you productive
  • 2
    Just the View of MVC
  • 1
    Sharable
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Split your UI into components with one true state
  • 1
    Fragments
  • 0
    Recharts
CONS OF REACT
  • 36
    Requires discipline to keep architecture organized
  • 23
    No predefined way to structure your app
  • 22
    Need to be familiar with lots of third party packages
  • 9
    JSX
  • 7
    Not enterprise friendly
  • 5
    One-way binding only
  • 2
    State consistency with backend neglected
  • 2
    Bad Documentation
  • 1
    Paradigms change too fast

related React posts

Vaibhav Taunk
Team Lead at Technovert | 31 upvotes 路 1.9M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Adebayo Akinlaja
Engineering Manager at Andela | 27 upvotes 路 1.1M views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen鈥攕ince I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more
Create React App logo

Create React App

980
916
4
Create React apps with no build configuration
980
916
+ 1
4
PROS OF CREATE REACT APP
  • 2
    No config, easy to use
  • 2
    Maintained by React core team
CONS OF CREATE REACT APP
  • 1
    No SSR

related Create React App posts

Adebayo Akinlaja
Engineering Manager at Andela | 27 upvotes 路 1.1M views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen鈥攕ince I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more

I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis 聽for cache and other time sensitive operations.

We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

See more
React.js Boilerplate logo

React.js Boilerplate

371
422
18
馃敟 Quick setup for performance orientated, offline-first React.js apps
371
422
+ 1
18
PROS OF REACT.JS BOILERPLATE
  • 4
    Amazing developer experience
  • 4
    Nice tooling
  • 3
    Easy setup
  • 3
    Easy offline first applications
  • 3
    Great documentation
  • 1
    Fast
CONS OF REACT.JS BOILERPLATE
    Be the first to leave a con

    related React.js Boilerplate posts

    React Router logo

    React Router

    2.1K
    1K
    12
    A complete routing solution for React.js
    2.1K
    1K
    + 1
    12
    PROS OF REACT ROUTER
    • 12
      Because there's not alternative
    CONS OF REACT ROUTER
      Be the first to leave a con

      related React Router posts

      ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

      ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

      React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

      styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

      React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

      Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

      See more

      I'm creating a website with React in my free time, and this is my first time doing this. So far, I've worked with React and React Router, but migrating to Next.js or Gatsby would cover Routing and SEO, which I currently cannot work with. Most things I read say that Next.js is the best solution, but I am trying to decide whether it is worth the time and effort to recreate the site for SEO and speed purposes. Does anyone have suggestions?

      See more
      styled-components logo

      styled-components

      1.3K
      520
      11
      Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps...
      1.3K
      520
      + 1
      11
      PROS OF STYLED-COMPONENTS
      • 11
        Very easy to use and integrate
      CONS OF STYLED-COMPONENTS
        Be the first to leave a con

        related styled-components posts

        Johnny Bell

        For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend.

        Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need.

        We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.

        Also we used React-Mentions for tagging tools and topics in the decisions. Typing @ will let you tag a tool, and typing # will allow you to tag a topic.

        The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li.

        If there are anymore tags you'd love to see added in the composer leave me a comment below and we will look into adding them.

        #StackDecisionsLaunch

        See more

        ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

        ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

        React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

        styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

        React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

        Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

        See more
        Storybook logo

        Storybook

        937
        462
        0
        Build bulletproof UI components faster
        937
        462
        + 1
        0
        PROS OF STORYBOOK
          Be the first to leave a pro
          CONS OF STORYBOOK
            Be the first to leave a con

            related Storybook posts

            Robert Zuber

            We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

            See more
            Ant Design logo

            Ant Design

            859
            1.4K
            225
            A set of high-quality React components
            859
            1.4K
            + 1
            225
            PROS OF ANT DESIGN
            • 43
              Lots of components
            • 34
              Polished and enterprisey look and feel
            • 22
              TypeScript
            • 20
              Easy to integrate
            • 18
              Es6 support
            • 17
              Beautiful and solid
            • 16
              Beautifully Animated Components
            • 15
              Quick Release rhythm
            • 14
              Great documentation
            • 14
              Typescript support
            • 11
              Short Code
            • 1
              Easy to customize Forms
            CONS OF ANT DESIGN
            • 18
              Less
            • 8
              Large File Size
            • 7
              Close
            • 4
              Poor accessibility support
            • 1
              Sdf
            • 1
              Dangerous to use as a base in component libraries
            • 1
              Gago
            • 0
              D

            related Ant Design posts

            Sarmad Chaudhary
            Founder & CEO at Ebiz Ltd. | 9 upvotes 路 525.8K views

            Hi there!

            I just want to have a simple poll/vote...

            If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:

            1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.

            2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.

            Your advice would help a lot! Thanks in advance :)

            See more
            Shared insights
            on
            Material-UIMaterial-UIAnt DesignAnt Design

            Hi, I start building an admin dashboard with next.js and looking for a frontend framework ( components ready ). So I end up with Ant Design and Material-UI, but I never built a project with these two.

            Here is a list of my requirements.

            1. Good documentation.
            2. easy CRUD ( date picker and date range picker bundled )
            3. built-in multi-lang feature or Great 3rd library support
            4. Admin dashboard template
            5. well code maintenance

            Which is better for the long run?

            See more
            Angular CLI logo

            Angular CLI

            843
            688
            0
            A command line interface for Angular
            843
            688
            + 1
            0
            PROS OF ANGULAR CLI
              Be the first to leave a pro
              CONS OF ANGULAR CLI
                Be the first to leave a con

                related Angular CLI posts

                Vaibhav Taunk
                Team Lead at Technovert | 31 upvotes 路 1.9M views

                I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

                See more

                Picked Angular 2 as framework since Angular CLI made it easy to get started on a self-contained frontend web project with TypeScript for easier development -- thanks to intellisense extensions for Visual Studio Code, hassle-free browser compatibility with the built-in Babel transpiler and packaging with the built-in Webpack configuration.

                See more