Set up a modern web app by running one command.

Overview

Create React App Build Status PRs Welcome

Logo

Create React apps with no build configuration.

Create React App works on macOS, Windows, and Linux.
If something doesn’t work, please file an issue.
If you have questions or need help, please ask in GitHub Discussions.

Quick Overview

npx create-react-app my-app
cd my-app
npm start

If you've previously installed create-react-app globally via npm install -g create-react-app, we recommend you uninstall the package using npm uninstall -g create-react-app or yarn global remove create-react-app to ensure that npx always uses the latest version.

(npx comes with npm 5.2+ and higher, see instructions for older npm versions)

Then open http://localhost:3000/ to see your app.
When you’re ready to deploy to production, create a minified bundle with npm run build.

npm start

Get Started Immediately

You don’t need to install or configure tools like webpack or Babel.
They are preconfigured and hidden so that you can focus on the code.

Create a project, and you’re good to go.

Creating an App

You’ll need to have Node 10.16.0 or later version on your local development machine (but it’s not required on the server). We recommend using the latest LTS version. You can use nvm (macOS/Linux) or nvm-windows to switch Node versions between different projects.

To create a new app, you may choose one of the following methods:

npx

npx create-react-app my-app

(npx is a package runner tool that comes with npm 5.2+ and higher, see instructions for older npm versions)

npm

npm init react-app my-app

npm init <initializer> is available in npm 6+

Yarn

yarn create react-app my-app

yarn create <starter-kit-package> is available in Yarn 0.25+

It will create a directory called my-app inside the current folder.
Inside that directory, it will generate the initial project structure and install the transitive dependencies:

my-app
├── README.md
├── node_modules
├── package.json
├── .gitignore
├── public
│   ├── favicon.ico
│   ├── index.html
│   └── manifest.json
└── src
    ├── App.css
    ├── App.js
    ├── App.test.js
    ├── index.css
    ├── index.js
    ├── logo.svg
    └── serviceWorker.js
    └── setupTests.js

No configuration or complicated folder structures, only the files you need to build your app.
Once the installation is done, you can open your project folder:

cd my-app

Inside the newly created project, you can run some built-in commands:

npm start or yarn start

Runs the app in development mode.
Open http://localhost:3000 to view it in the browser.

The page will automatically reload if you make changes to the code.
You will see the build errors and lint warnings in the console.

Build errors

npm test or yarn test

Runs the test watcher in an interactive mode.
By default, runs tests related to files changed since the last commit.

Read more about testing.

npm run build or yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.

Your app is ready to be deployed.

User Guide

You can find detailed instructions on using Create React App and many tips in its documentation.

How to Update to New Versions?

Please refer to the User Guide for this and other information.

Philosophy

  • One Dependency: There is only one build dependency. It uses webpack, Babel, ESLint, and other amazing projects, but provides a cohesive curated experience on top of them.

  • No Configuration Required: You don't need to configure anything. A reasonably good configuration of both development and production builds is handled for you so you can focus on writing code.

  • No Lock-In: You can “eject” to a custom setup at any time. Run a single command, and all the configuration and build dependencies will be moved directly into your project, so you can pick up right where you left off.

What’s Included?

Your environment will have everything you need to build a modern single-page React app:

  • React, JSX, ES6, TypeScript and Flow syntax support.
  • Language extras beyond ES6 like the object spread operator.
  • Autoprefixed CSS, so you don’t need -webkit- or other prefixes.
  • A fast interactive unit test runner with built-in support for coverage reporting.
  • A live development server that warns about common mistakes.
  • A build script to bundle JS, CSS, and images for production, with hashes and sourcemaps.
  • An offline-first service worker and a web app manifest, meeting all the Progressive Web App criteria. (Note: Using the service worker is opt-in as of [email protected] and higher)
  • Hassle-free updates for the above tools with a single dependency.

Check out this guide for an overview of how these tools fit together.

The tradeoff is that these tools are preconfigured to work in a specific way. If your project needs more customization, you can "eject" and customize it, but then you will need to maintain this configuration.

Popular Alternatives

Create React App is a great fit for:

  • Learning React in a comfortable and feature-rich development environment.
  • Starting new single-page React applications.
  • Creating examples with React for your libraries and components.

Here are a few common cases where you might want to try something else:

  • If you want to try React without hundreds of transitive build tool dependencies, consider using a single HTML file or an online sandbox instead.

  • If you need to integrate React code with a server-side template framework like Rails, Django or Symfony, or if you’re not building a single-page app, consider using nwb, or Neutrino which are more flexible. For Rails specifically, you can use Rails Webpacker. For Symfony, try Symfony's webpack Encore.

  • If you need to publish a React component, nwb can also do this, as well as Neutrino's react-components preset.

  • If you want to do server rendering with React and Node.js, check out Next.js or Razzle. Create React App is agnostic of the backend, and only produces static HTML/JS/CSS bundles.

  • If your website is mostly static (for example, a portfolio or a blog), consider using Gatsby or Next.js. Unlike Create React App, Gatsby pre-renders the website into HTML at build time. Next.js supports both server rendering and pre-rendering.

  • Finally, if you need more customization, check out Neutrino and its React preset.

All of the above tools can work with little to no configuration.

If you prefer configuring the build yourself, follow this guide.

React Native

Looking for something similar, but for React Native?
Check out Expo CLI.

Contributing

We'd love to have your helping hand on create-react-app! See CONTRIBUTING.md for more information on what we're looking for and how to get started.

Supporting Create React App

Create React App is a community maintained project and all contributors are volunteers. If you'd like to support the future development of Create React App then please consider donating to our Open Collective.

Credits

This project exists thanks to all the people who contribute.

Thanks to Netlify for hosting our documentation.

Acknowledgements

We are grateful to the authors of existing related projects for their ideas and collaboration:

License

Create React App is open source software licensed as MIT. The Create React App logo is licensed under a Creative Commons Attribution 4.0 International license.

Comments
  • Add runtime error overlay

    Add runtime error overlay

    If you would like to help, please see https://github.com/facebookincubator/create-react-app/issues/1129.


    This PR is a prototype implementation for #783 which hopefully gets the ball rolling.

    This is by no means a complete or even polished proposal, but simply a WIP to track the ongoing discussion in #783 as it unfolds. There is much to be done for DX and message clarity when the Error object is unavailable or unparsable.

    Errors

    Errors are captured using window.onerror. window.onerror provides the Error object in most all modern browsers: Chrome 46(?), Firefox 31, IE 11, and Safari 10(ref). Notably, support is missing from Microsoft Edge (unverified, see here -- can someone test this please?).

    Unhandled Rejections

    Unfortunately, there seems to be no standard/proper way to capture unhandled rejection -- Chrome seems to be the only browser doing this, exposed via the unhandledrejection event. Does anyone have any ideas on how to accomplish this / should it be a Chrome only feature?


    CLA Signed tag: new feature 
    opened by Timer 262
  • npm ERR! 404 Not Found - GET https://registry.npmjs.org/error-ex

    npm ERR! 404 Not Found - GET https://registry.npmjs.org/error-ex

    Describe the bug

    Below error comes when creating new project

    C:\Personal\web-projects\React>npx create-react-app pomodoro-clock
    npx: installed 99 in 16.973s
    
    Creating a new React app in C:\Personal\web-projects\React\pomodoro-clock.
    
    Installing packages. This might take a couple of minutes.
    Installing react, react-dom, and react-scripts with cra-template...
    
    npm ERR! code E404
    npm ERR! 404 Not Found - GET https://registry.npmjs.org/error-ex
    npm ERR! 404
    npm ERR! 404  'error-ex@^1.3.1' is not in the npm registry.
    npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
    npm ERR! 404 It was specified as a dependency of 'parse-json'
    npm ERR! 404
    npm ERR! 404 Note that you can also install from a
    npm ERR! 404 tarball, folder, http url, or git url.
    

    When I try to go to https://registry.npmjs.org/error-ex it returns a 404 Same issue when using command npm init react-app my-app

    Did you try recovering your dependencies?

    Yes

    Environment

    Environment Info:
    
      current version of create-react-app: 3.3.1
      running from C:\Users\username\AppData\Roaming\npm-cache\_npx\21236\node_modules\create-react-app
    
      System:
        OS: Windows 10 10.0.17763
        CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
      Binaries:
        Node: 12.13.1 - C:\Program Files\nodejs\node.EXE
        Yarn: Not Found
        npm: 6.13.7 - C:\Program Files\nodejs\npm.CMD
      Browsers:
        Edge: 44.17763.831.0
        Internet Explorer: 11.0.17763.771
      npmPackages:
        react: Not Found
        react-dom: Not Found
        react-scripts: Not Found
      npmGlobalPackages:
        create-react-app: Not Found
    

    Steps to reproduce

    1. Create new project with npx create-react-app project-name. Last created a project successfully last week using the same PC
    needs triage issue: bug report 
    opened by acskck 213
  • Browserslist error

    Browserslist error

    Hello, i just used 'npx create-react-app project-name' and when im starting my project im getting this error:

    /src/index.css (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./src/index.css) BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query. at Array.reduce () at Array.some () at Array.filter ()

    Npm -v : 6.9.0 Node -v : v10.16.0

    opened by razvan-soare 161
  • Why was service worker merged into create react app?

    Why was service worker merged into create react app?

    I use create create app for teaching and I don't see the benefit in making stuff more complicated with adding so much advanced boilerplate code.

    You probably know that service worker won't work on any iOS device (20% - 25% of all your users) and this is not about to change soon (maybe never).

    Adding service workers by default is about to create very different experiences and bug behaviour depending on the device. It also makes it way more complicated to get a create react app to work offline for all platforms.

    Please don't turn cra into something like a Windows98 computer where you had to remove AOL and other preinstalled stuff before being able to be productive.

    issue: proposal issue: question > PWA 
    opened by jantimon 154
  • General feedback

    General feedback

    Let’s use this thread for a general discussion.

    Does the flow feel good? Did we pick the right plugins, presets, and loaders? Do you see areas for improvement?

    This project is in a very early stage so there’s plenty of all hanging fruit if you’d like to make React experience better.

    Thanks for taking a look at this project!

    issue: proposal 
    opened by gaearon 152
  • Last call for Create React App v2

    Last call for Create React App v2

    Hi everyone! We just released what we hope to be the last beta before v2 is marked stable and tagged latest on npm tomorrow.

    Please try it as soon as possible and let us know if you run into any issues!

    Create new application:

    $ npx create-react-app@next --scripts-version=@next test-next
    

    Upgrade existing:

    $ npm install react-scripts@next --save
    $ # or
    $ yarn add react-scripts@next
    

    Here's a draft of the release notes:

    Create React App v2.0.1

    New Features

    1. Updated tooling: Babel 7, webpack 4, Jest 23
    2. Packages using new JavaScript features in node_modules now work
    3. Automatic vendor bundles and long term caching
    4. CSS Modules
    5. Sass Support
    6. SVGs as React Components
    7. Babel Macros
    8. Targetable CSS support, with automatic polyfills and prefixing

    Migrating from 1.1.15 to 2.0.1

    Inside any created project that has not been ejected, run:

    $ npm install --save --save-exact [email protected]
    $ # or
    $ yarn add --exact [email protected]
    

    Next, follow the migration instructions below that are relevant to you.

    You may no longer code split with require.ensure()

    We previously allowed code splitting with a webpack-specific directive, require.ensure(). It is now disabled in favor of import().

    To switch to import(), follow the examples below:

    Single Module

    require.ensure(['module-a'], function() {
      var a = require('module-a');
      // ...
    });
        
    // Replace with:
    import('module-a').then(a => {
      // ...
    });
    

    Multiple Module

    require.ensure(['module-a', 'module-b'], function() {
      var a = require('module-a');
      var b = require('module-b');
      // ...
    });
        
    // Replace with:
    Promise.all([import('module-a'), import('module-b')]).then(([a, b]) => {
      // ...
    });
    

    The default Jest environment was changed to jsdom

    Look at the test entry in the scripts section of your package.json. Here's a table how to change it from "before" and "after", depending on what you have there:

    | 1.x (if you have this...) | 2.x (...change it to this!) | | - | - | | react-scripts test --env=jsdom | react-scripts test | | react-scripts test | react-scripts test --env=node |

    .mjs file extension support was removed

    Change the extension of any files in your project using .mjs to just .js.

    It was removed because of inconsistent support from underlying tools. We will add it back after it stops being experimental, and Jest gets built-in support for it.

    Move advanced proxy configuration to src/setupProxy.js

    This change is only required for individuals who used the advanced proxy configuration in v1.

    To check if action is required, look for the proxy key in package.json. Then, follow the table below.

    1. I couldn't find a proxy key in package.json
      • No action is required!
    2. The value of proxy is a string (e.g. http://localhost:5000)
      • No action is required!
    3. The value of proxy is an object
      • Follow the migration instructions below.

    If your proxy is an object, that means you are using the advanced proxy configuration.

    Again, if your proxy field is a string, e.g. http://localhost:5000, you do not need to do anything. This feature is still supported and has the same behavior.

    First, install http-proxy-middleware using npm or Yarn:

    $ npm install http-proxy-middleware --save
    $ # or
    $ yarn add http-proxy-middleware
    

    Next, create src/setupProxy.js and place the following contents in it:

    const proxy = require('http-proxy-middleware')
        
    module.exports = function(app) {
      // ...
    }
    

    Now, migrate each entry in your proxy object one by one, e.g.:

    "proxy": {
      "/api": {
        "target": "http://localhost:5000/"
        },
      "/*.svg": {
        "target": "http://localhost:5000/"
      }
    }
    

    Place entries into src/setupProxy.js like so:

    const proxy = require('http-proxy-middleware')
     
    module.exports = function(app) {
      app.use(proxy('/api', { target: 'http://localhost:5000/' }))
      app.use(proxy('/*.svg', { target: 'http://localhost:5000/' }))
    }
    

    You can also use completely custom logic there now! This wasn't possible before.

    Internet Explorer is no longer supported by default (but you can opt in!)

    We have dropped default support for Internet Explorer 9, 10, and 11. If you still need to support these browsers, follow the instructions below.

    First, install react-app-polyfill:

    $ npm install react-app-polyfill --save
    $ # or
    $ yarn add react-app-polyfill
    

    Next, place one of the following lines at the very top of src/index.js:

    import 'react-app-polyfill/ie9'; // For IE 9-11 support
    import 'react-app-polyfill/ie11'; // For IE 11 support
    

    You can read more about these polyfills here.

    The behavior of a CommonJS import() has changed

    Webpack 4 changed the behavior of import() to be closer in line with the specification.

    Previously, importing a CommonJS module did not require you specify the default export. In most cases, this is now required. If you see errors in your application about ... is not a function, you likely need to update your dynamic import, e.g.:

    const throttle = await import("lodash/throttle");
    // replace with
    const throttle = await import("lodash/throttle").then(m => m.default);
    

    Anything missing?

    This was a large release, and we might have missed something.

    Please file an issue and we will try to help.

    Migrating from 2.0.0-next.xyz

    If you used 2.x alphas, please follow these instructions.

    Detailed Changelog

    >> TODO <<

    issue: announcement 
    opened by Timer 144
  • npm run build fails for EventEmitter

    npm run build fails for EventEmitter

    @gaearon asked that I file a separate issue.

    How to reproduce: run create-react-app fail-event-emitter, add a line

    import EventEmitter from 'events';
    

    to src/index.js and then run npm run build, which fails with:

    > [email protected] build /home/gback/fail-event-emitter
    > react-scripts build
    
    Creating an optimized production build...
    Failed to compile.
    
    static/js/main.068c41be.js from UglifyJs
    Unexpected character '`' [/usr/lib/nodejs/events.js:260,0]
    

    react-scripts 0.7.0 is used and node.js 6.9.1 (or 7.0)

    The purported cause is that CRA does not transpile "dependencies" into ES5 and then the UglifyJS plugin fails when it encounters ES6 code. The test case above was derived from a failure in react-bootstrap-tables, which includes a module that in turn references EventEmitter. Others have suggested to provide an alternate EventEmitter implementation in the application path, but it is not clear to me how react-bootstrap-table's dependencies can be made to use this alternate implementation.

    issue: bug contributions: up for grabs! tag: underlying tools 
    opened by godmar 130
  • serve bundles and app under homepage path

    serve bundles and app under homepage path

    Verified by adding homepage to package.json, and confirming that it would display the subpath in the terminal, and open the browser with the sub path in the url.

    tested by editing both js and css to verify hot loading works the same as before.

    Then verified that if I take homepage back out of package.json, it works as intended.

    screen shot 2017-03-23 at 9 21 51 am screen shot 2017-03-23 at 9 21 40 am

    CLA Signed 
    opened by kellyrmilligan 126
  • Error: EPERM: operation not permitted, mkdir 'C:\Users\Vaidehi' TypeError: Cannot read property 'get' of undefined

    Error: EPERM: operation not permitted, mkdir 'C:\Users\Vaidehi' TypeError: Cannot read property 'get' of undefined

    Im trying to create a react app using command create-react-app and getting the error of, Screenshot (114)

    MY COMMAND: (using . as i want to create the app in the current folder itself)

    C:\Users\Vaidehi Shah\Desktop\MERN-ShoppingList\client> npx create-react-app .

    ERROR MESSAGE:

    Error: EPERM: operation not permitted, mkdir 'C:\Users\Vaidehi' TypeError: Cannot read property 'get' of undefined at errorMessage (C:\Program Files\nodejs\node_modules\npm\lib\utils\error-message.js:38:39) at errorHandler (C:\Program Files\nodejs\node_modules\npm\lib\utils\error-handler.js:201:13) at C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js:78:20 at cb (C:\Program Files\nodejs\node_modules\npm\lib\npm.js:225:22) at C:\Program Files\nodejs\node_modules\npm\lib\npm.js:263:24 at C:\Program Files\nodejs\node_modules\npm\lib\config\core.js:81:7 at Array.forEach () at C:\Program Files\nodejs\node_modules\npm\lib\config\core.js:80:13 at f (C:\Program Files\nodejs\node_modules\npm\node_modules\once\once.js:25:25) at afterExtras (C:\Program Files\nodejs\node_modules\npm\lib\config\core.js:171:20) C:\Program Files\nodejs\node_modules\npm\lib\utils\error-handler.js:97 var doExit = npm.config.loaded ? npm.config.get('_exit') : true ^

    TypeError: Cannot read property 'loaded' of undefined at exit (C:\Program Files\nodejs\node_modules\npm\lib\utils\error-handler.js:97:27) at process.errorHandler (C:\Program Files\nodejs\node_modules\npm\lib\utils\error-handler.js:216:3) at process.emit (events.js:210:5) at process._fatalException (internal/process/execution.js:150:25) Install for [ 'create-react-app@latest' ] failed with code 7

    opened by vaidehishah07 120
  • 4.0.0 breaks with typescript (all versions)

    4.0.0 breaks with typescript (all versions)

    Describe the bug

    I made a clean install of cra@next with typescript and then upgraded typescript to 4.1.0-beta ( also tested 4.1.0-dev.20201023 )

    npx create-react-app@next --scripts-version=@next --template=typescript@next my-ts-app
    
    $$$ then replaced typescript 4.0.3 with 4.1.0-beta ( or ^4.1.0-beta ) in package.json
    
    rm -rf node_modules package-lock.json && npm i
    
    npm start
    

    Error message:

    node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239
          appTsConfig.compilerOptions[option] = value;
                                              ^
    
    TypeError: Cannot assign to read only property 'jsx' of object '#<Object>'
    

    ( EDIT: This doesn't happen with cra 4.0.0-next.98 )

    Did you try recovering your dependencies?

    Yes

    Which terms did you search for in User Guide?

    I just looked for typescript bugs reported and closed in the last few days

    Environment

    System: OS: macOS 10.15.7 CPU: (8) x64 Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Binaries: Node: 14.14.0 - /usr/local/bin/node Yarn: Not Found npm: 6.14.8 - /usr/local/bin/npm Browsers: Chrome: 86.0.4240.111 Firefox: Not Found Safari: 14.0 npmPackages: react: ^17.0.1 => 17.0.1 react-dom: ^17.0.1 => 17.0.1 react-scripts: 4.0.0-next.117 => 4.0.0-next.117 npmGlobalPackages: create-react-app: Not Found

    Steps to reproduce

    1. npx create-react-app@next --scripts-version=@next --template=typescript@next my-ts-app

    2. replace typescript 4.0.3 with 4.1.0-beta ( or ^4.1.0-beta ) in package.json

    3. rm -rf node_modules package-lock.json && npm i

    4. npm start

    Expected behavior

    Should work out of the box

    Actual behavior

    node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239
          appTsConfig.compilerOptions[option] = value;
                                              ^
    
    TypeError: Cannot assign to read only property 'jsx' of object '#<Object>'
    

    Reproducible demo

    Steps are simple enough to build your own demo

    issue: bug 
    opened by benneq 117
  • Hot Reload stopped working with React

    Hot Reload stopped working with React "^17.0.1"

    Describe the bug

    Hot reloading when the redux-state change stopped working when I use CRA to get the last React version. Noticed that it is due to React version and I made a test creating a new react project, as a result the package.json shows

    "dependencies": {
        "@testing-library/jest-dom": "^5.11.5",
        "@testing-library/react": "^11.1.0",
        "@testing-library/user-event": "^12.1.10",
        "react": "^17.0.1",
        "react-dom": "^17.0.1",
        "react-redux": "^7.2.1",
        "react-scripts": "4.0.0",
        "redux": "^4.0.5",
        "web-vitals": "^0.2.4"
      },
    

    then change it to a previous version of react (copied from an old project)

    "dependencies": {
        "@testing-library/jest-dom": "^4.2.4",
        "@testing-library/react": "^9.5.0",
        "@testing-library/user-event": "^7.2.1",
        "react": "^16.13.1",
        "react-dom": "^16.13.1",
        "react-redux": "^7.2.1",
        "react-scripts": "3.4.3",
        "redux": "^4.0.5"
      },
    

    And it continue to works as always.

    Did you try recovering your dependencies?

    yes

    Environment

    current version of create-react-app: 4.0.0 running from C:\Users\stewa\AppData\Roaming\npm\node_modules\create-react-app

    System: OS: Windows 10 10.0.19041 Binaries: Node: 12.9.1 - C:\Program Files\nodejs\node.EXE Yarn: Not Found npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD Browsers: Chrome: 86.0.4240.111 Edge: Spartan (44.19041.423.0), Chromium (86.0.622.51)
    Internet Explorer: 11.0.19041.1 npmPackages: react: ^17.0.1 => 17.0.1 react-dom: ^17.0.1 => 17.0.1 react-scripts: 4.0.0 => 4.0.0 npmGlobalPackages: create-react-app: Not Found

    Steps to reproduce

    (Write your steps here:)

    1. I have a file with a state with this value in my Redux reducer
    const initialState = [
      {
        id: Date.now(),
        task: "new todo ",
        completed: false,
      }
    ];
    
    1. Modify the object in the file to this
    const initialState = [
      {
        id: 1,
        task: "new todo ",
        completed: false,
      },
      {
        id:123,
        task: "new todo ",
        completed: false,
      }
    ];
    
    1. As previous versions of React / CRA the page force a reload, displaying in the page the new object added, but it's not anymore

    Expected behavior

    Even if you change the text of one of the objects in the reducer it used to reload the page. I'm expecting to see the new state in the page as I save a file when the state change

    Actual behavior

    alt text

    Here you can see I saved the file and the page is not showing the new state, and the new data.

    Reproducible demo

    https://github.com/StewartGF/todo-test

    I created this clean project with CRA, it has react v17 You can change the version in the package.json to what I paste in the description and use npm install in order to see the project working as it was working in previous versions.

    issue: needs investigation needs triage issue: bug report 
    opened by StewartGF 115
  • eslint was conflict

    eslint was conflict

    Describe the bug

    (Write your answer here.) image

    Did you try recovering your dependencies?

    (Write your answer here.) Yes. I upgrade all my packages and npm and node and OS and hardware.

    Which terms did you search for in User Guide?

    (Write your answer here if relevant.) Nothing about this bug in guid.

    Environment

    (paste the output of the command here.) BROWSER=none

    Steps to reproduce

    (Write your steps here:)

    Expected behavior

    (Write what you thought would happen.)

    Actual behavior

    (Write what happened. Please add screenshots!)

    Reproducible demo

    (Paste the link to an example project and exact instructions to reproduce the issue.)

    		"@typescript-eslint/eslint-plugin": "^5.48.0",
    		"@typescript-eslint/parser": "^5.48.0",
    		"eslint": "^8.31.0",
    		"eslint-config-airbnb": "^19.0.4",
    		"eslint-plugin-html": "^7.1.0",
    		"eslint-plugin-import": "^2.26.0",
    		"eslint-plugin-jsonc": "^2.5.0",
    		"eslint-plugin-jsx-a11y": "^6.6.1",
    		"eslint-plugin-markdown": "^3.0.0",
    		"eslint-plugin-no-secrets": "^0.8.9",
    		"eslint-plugin-optimize-regex": "^1.2.1",
    		"eslint-plugin-react": "^7.31.11",
    		"eslint-plugin-react-hooks": "^4.6.0",
    		"eslint-plugin-security": "^1.5.0",
    
    		"react-scripts": "^5.0.1",
    		"typescript": "^4.9.4",
    

    I think trouble with this pkg "eslint-config-react-app": "^7.0.1",

    needs triage issue: bug report 
    opened by cybermerlin 1
  • Npm start says something is running on EVERY port I try but serve -s build works fine on any port I use...

    Npm start says something is running on EVERY port I try but serve -s build works fine on any port I use...

    Describe the bug

    Npm start says something is running on EVERY port I try but serve -s build works fine on any port I use...

    Did you try recovering your dependencies?

    9.2.0

    Which terms did you search for in User Guide?

    (Write your answer here if relevant.)

    Environment

    (paste the output of the command here.)

    Steps to reproduce

    (Write your steps here:)

    1. npm start

    Expected behavior

    see the server up and running

    (Write what you thought would happen.)

    Actual behavior

    ✔ Something is already running on port 3000.

    Would you like to run the app on another port instead? … no

    Reproducible demo

    (Paste the link to an example project and exact instructions to reproduce the issue.)

    needs triage issue: bug report 
    opened by bostonmacosx 1
  • Mamis

    Mamis

    Describe the bug

    (Write your answer here.)

    Did you try recovering your dependencies?

    (Write your answer here.)

    Which terms did you search for in User Guide?

    (Write your answer here if relevant.)

    Environment

    (paste the output of the command here.)

    Steps to reproduce

    (Write your steps here:)

    Expected behavior

    (Write what you thought would happen.)

    Actual behavior

    (Write what happened. Please add screenshots!)

    Reproducible demo

    (Paste the link to an example project and exact instructions to reproduce the issue.)

    needs triage issue: bug report 
    opened by Sandant589 1
  • docs: fix external links in

    docs: fix external links in "Adding a Router"

    1. Changed https://reactrouter.com/docs/examples/basic (404) to https://v5.reactrouter.com/web/example/basic
    2. Changed https://reactrouter.com/docs/getting-started/tutorial#add-some-routes (404) to https://reactrouter.com/en/start/tutorial#adding-a-router
    CLA Signed 
    opened by paramt 3
  • nth-check  <2.0.1 Severity: high &&  json5  <2.2.2 Severity: high

    nth-check <2.0.1 Severity: high && json5 <2.2.2 Severity: high

    json5 <2.2.2 Severity: high Prototype Pollution in JSON5 via Parse Method - https://github.com/advisories/GHSA-9c47-m6qq-7p4h fix available via npm audit fix --force Will install [email protected], which is a breaking change node_modules/tsconfig-paths/node_modules/json5 tsconfig-paths 3.5.0 - 3.9.0 || 3.11.0 - 3.14.1 Depends on vulnerable versions of json5 node_modules/tsconfig-paths eslint-plugin-import >=2.24.2 Depends on vulnerable versions of tsconfig-paths node_modules/eslint-plugin-import eslint-config-react-app >=7.0.0-next.75 Depends on vulnerable versions of eslint-plugin-import node_modules/eslint-config-react-app react-scripts >=2.1.4 Depends on vulnerable versions of @svgr/webpack Depends on vulnerable versions of eslint-config-react-app node_modules/react-scripts

    nth-check <2.0.1 Severity: high Inefficient Regular Expression Complexity in nth-check - https://github.com/advisories/GHSA-rp65-9cf3-cjxr fix available via npm audit fix --force Will install [email protected], which is a breaking change node_modules/svgo/node_modules/nth-check css-select <=3.1.0 Depends on vulnerable versions of nth-check node_modules/svgo/node_modules/css-select svgo 1.0.0 - 1.3.2 Depends on vulnerable versions of css-select node_modules/svgo @svgr/plugin-svgo <=5.5.0 Depends on vulnerable versions of svgo node_modules/@svgr/plugin-svgo @svgr/webpack 4.0.0 - 5.5.0 Depends on vulnerable versions of @svgr/plugin-svgo node_modules/@svgr/webpack react-scripts >=2.1.4 Depends on vulnerable versions of @svgr/webpack Depends on vulnerable versions of eslint-config-react-app

    needs triage issue: bug report 
    opened by alk-m90387 2
Releases(v5.0.1)
  • v5.0.1(Apr 12, 2022)

    5.0.1 (2022-04-12)

    Create React App 5.0.1 is a maintenance release that improves compatibility with React 18. We've also updated our templates to use createRoot and relaxed our check for older versions of Create React App.

    Migrating from 5.0.0 to 5.0.1

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    

    :bug: Bug Fix

    :nail_care: Enhancement

    • cra-template-typescript, cra-template, react-scripts
    • cra-template-typescript, cra-template
    • eslint-config-react-app

    :memo: Documentation

    :house: Internal

    Committers: 11

    Source code(tar.gz)
    Source code(zip)
  • v5.0.0(Dec 14, 2021)

    v5.0.0 (2021-12-14)

    Create React App 5.0 is a major release with several new features and the latest version of all major dependencies.

    Thanks to all the maintainers and contributors who worked so hard on this release! 🙌

    Highlights

    • webpack 5 (#11201)
    • Jest 27 (#11338)
    • ESLint 8 (#11375)
    • PostCSS 8 (#11121)
    • Fast Refresh improvements and bug fixes (#11105)
    • Support for Tailwind (#11717)
    • Improved package manager detection (#11322)
    • Unpinned all dependencies for better compatibility with other tools (#11474)
    • Dropped support for Node 10 and 12

    Migrating from 4.0.x to 5.0.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    

    NOTE: You may need to delete your node_modules folder and reinstall your dependencies by running npm install (or yarn) if you encounter errors after upgrading.

    If you previously ejected but now want to upgrade, one common solution is to find the commits where you ejected (and any subsequent commits changing the configuration), revert them, upgrade, and later optionally eject again. It’s also possible that the feature you ejected for is now supported out of the box.

    Breaking Changes

    Like any major release, [email protected] contains a number of breaking changes. We expect that they won't affect every user, but we recommend you look over this section to see if something is relevant to you. If we missed something, please file a new issue.

    Dropped support for Node 10 and 12

    Node 10 reached End-of-Life in April 2021 and Node 12 will be End-of-Life in April 2022. Going forward we will only support the latest LTS release of Node.js.

    Full Changelog

    :boom: Breaking Change

    • create-react-app
    • babel-preset-react-app, cra-template-typescript, cra-template, create-react-app, eslint-config-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • eslint-config-react-app, react-error-overlay, react-scripts
    • react-scripts

    :bug: Bug Fix

    :nail_care: Enhancement

    • react-scripts
      • #11717 Add support for Tailwind (@iansu)
      • #8227 Add source-map-loader for debugging into original source of node_modules libraries that contain sourcemaps (@justingrant)
      • #10499 Remove ESLint verification when opting-out (@mrmckeb)
    • eslint-config-react-app, react-error-overlay, react-scripts
    • create-react-app
    • react-dev-utils
      • #11105 fix: fast refresh stops on needed bail outs (@pmmmwh)
      • #10205 Update ModuleNotFoundPlugin to support Webpack 5 (@raix)
    • create-react-app, react-scripts

    :memo: Documentation

    :house: Internal

    • Other
    • create-react-app
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • react-scripts
    • babel-plugin-named-asset-import, confusing-browser-globals, create-react-app, eslint-config-react-app, react-dev-utils, react-error-overlay, react-scripts
    • confusing-browser-globals, cra-template-typescript, cra-template, create-react-app
    • react-error-overlay, react-scripts
    • babel-preset-react-app, cra-template-typescript, cra-template, create-react-app, eslint-config-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts

    :hammer: Underlying Tools

    • react-dev-utils, react-scripts
    • react-scripts
    • babel-plugin-named-asset-import, confusing-browser-globals, create-react-app, react-dev-utils, react-error-overlay, react-scripts
      • #11338 Upgrade jest and related packages from 26.6.0 to 27.1.0 (@krreet)
    • eslint-config-react-app, react-error-overlay, react-scripts
    • babel-preset-react-app, react-dev-utils, react-error-overlay, react-scripts
    • react-dev-utils

    Committers: 34

    Source code(tar.gz)
    Source code(zip)
  • v4.0.3(Feb 22, 2021)

    4.0.3 (2021-02-22)

    v4.0.3 is a maintenance release that includes minor bug fixes and dependency updates.

    :bug: Bug Fix

    • react-scripts

    :house: Internal

    • react-dev-utils
      • #10412 update immer to 8.0.1 to address vulnerability (@wclem4)
    • create-react-app

    Committers: 4

    Migrating from 4.0.2 to 4.0.3

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v4.0.2(Feb 3, 2021)

    4.0.2 (2021-02-03)

    v4.0.2 is a maintenance release that includes minor bug fixes and documentation updates.

    :rocket: New Feature

    • react-scripts
      • #8986 Add support for new BUILD_PATH advanced configuration variable (@ajhyndman)

    :bug: Bug Fix

    • react-scripts
      • #10170 Add opt-out for eslint-webpack-plugin (@mrmckeb)
      • #9872 fix(react-scripts): add missing peer dependency react and update react-refresh-webpack-plugin (@merceyz)
      • #9964 Add TypeScript 4.x as peerDependency to react-scripts (@sheepsteak)

    :nail_care: Enhancement

    • react-scripts

    :memo: Documentation

    :house: Internal

    :hammer: Underlying Tools

    Committers: 15

    Source code(tar.gz)
    Source code(zip)
  • v4.0.1(Nov 23, 2020)

    v4.0.1 is a maintenance release that includes minor bug fixes and documentation updates.

    :bug: Bug Fix

    • react-scripts
    • react-dev-utils
      • #9884 fix: page doesn't get refreshed when FAST_REFRESH=false (@n3tr)

    :nail_care: Enhancement

    :memo: Documentation

    • #10052 docs: add React Testing Library as a library requiring jsdom (@anyulled)

    :house: Internal

    Committers: 9

    Migrating from 4.0.0 to 4.0.1

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v4.0.0(Oct 23, 2020)

    4.0.0 (2020-10-23)

    Create React App 4.0 is a major release with several new features, including support for Fast Refresh!

    Thanks to all the maintainers and contributors who worked so hard on this release! :raised_hands:

    Highlights

    • Fast Refresh #8582
    • React 17 support
      • New JSX transform #9645
    • TypeScript 4 support #9734
    • ESLint 7 #8978
      • New Jest and React Testing Library rules #8963
    • Jest 26 #8955
    • PWA/workbox improvements
      • Switch to the Workbox InjectManifest plugin #9205
      • Now its own template so it can be released independently
    • Web Vitals support #9116

    Migrating from 3.4.x to 4.0.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    

    NOTE: You may need to delete your node_modules folder and reinstall your dependencies by running yarn (or npm install) if you encounter errors after upgrading.

    If you previously ejected but now want to upgrade, one common solution is to find the commits where you ejected (and any subsequent commits changing the configuration), revert them, upgrade, and later optionally eject again. It’s also possible that the feature you ejected for is now supported out of the box.

    Breaking Changes

    Like any major release, [email protected] contains a number of breaking changes. We expect that they won't affect every user, but we recommend you look over this section to see if something is relevant to you. If we missed something, please file a new issue.

    ESLint

    We've upgraded to ESLint 7 and added many new rules including some for Jest and React Testing Library as well as the import/no-anonymous-default-export rule. We've also upgraded eslint-plugin-hooks to version 4.0.0 and removed the EXTEND_ESLINT flag as it is no longer required to customize the ESLint config.

    Jest

    We've upgraded to Jest 26 and now set resetMocks to true by default in the Jest config.

    Service workers

    We've switched to the Workbox InjectManifest plugin and moved the PWA templates into their own repository.

    Removed typescript flag and NODE_PATH support

    We've removed the deprecated typescript flag when creating a new app. Use --template typescript instead. We've also dropped deprecated NODE_PATH flag as this has been replaced by setting the base path in jsconfig.json.

    Fix dotenv file loading order

    We've changed the loading order of env files to match the dotenv specification. See #9037 for more details.

    Dropped Node 8 support

    Node 8 reached End-of-Life at the end of 2019 and is no longer supported.

    Detailed Changelog

    :rocket: New Feature

    • eslint-config-react-app, react-error-overlay, react-scripts
    • react-scripts
    • create-react-app
      • #9359 feat: exit on outdated create-react-app version (@mrmckeb)
    • cra-template-typescript, cra-template, react-scripts
    • react-dev-utils, react-scripts

    :boom: Breaking Change

    • eslint-config-react-app, react-error-overlay, react-scripts
    • cra-template-typescript, cra-template, eslint-config-react-app, react-error-overlay, react-scripts
    • eslint-config-react-app
    • create-react-app
      • #9359 feat: exit on outdated create-react-app version (@mrmckeb)
    • cra-template-typescript, cra-template, react-scripts
    • babel-plugin-named-asset-import, confusing-browser-globals, create-react-app, react-dev-utils, react-error-overlay, react-scripts
    • create-react-app, react-scripts
      • #8934 feat: remove typescript flag and NODE_PATH support (@mrmckeb)
    • react-scripts
    • babel-plugin-named-asset-import, babel-preset-react-app, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • eslint-config-react-app, react-scripts
    • cra-template-typescript, cra-template, create-react-app, react-app-polyfill, react-dev-utils, react-scripts
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, cra-template-typescript, react-dev-utils, react-error-overlay, react-scripts

    :bug: Bug Fix

    • react-scripts
    • babel-preset-react-app, eslint-config-react-app, react-scripts
    • eslint-config-react-app, react-scripts
    • create-react-app
    • babel-preset-react-app
      • #9374 fix: use default modules option from preset-env (@JLHwung)
    • react-dev-utils
    • react-dev-utils, react-scripts
    • cra-template-typescript, cra-template, react-scripts
      • #8734 fix: handle templates without main package field (@mrmckeb)

    :nail_care: Enhancement

    • react-scripts
    • babel-preset-react-app, eslint-config-react-app, react-scripts
    • cra-template
    • babel-preset-react-app, react-scripts
    • react-dev-utils, react-scripts
      • #9350 Add Fast Refresh warning when using React < 16.10 (@iansu)
    • react-dev-utils, react-error-overlay, react-scripts
    • cra-template-typescript, cra-template
    • create-react-app

    :memo: Documentation

    :house: Internal

    :hammer: Underlying Tools

    • react-scripts
    • react-error-overlay, react-scripts
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, cra-template-typescript, cra-template, create-react-app, eslint-config-react-app, react-app-polyfill, react-error-overlay, react-scripts
    • eslint-config-react-app, react-dev-utils, react-scripts
      • #9751 Replace deprecated eslint-loader by eslint-webpack-plugin (@tooppaaa)
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, cra-template-typescript, cra-template, create-react-app, eslint-config-react-app, react-dev-utils, react-error-overlay, react-scripts
    • eslint-config-react-app, react-error-overlay, react-scripts
    • cra-template-typescript, cra-template
    • react-app-polyfill
    • react-dev-utils
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, react-dev-utils, react-error-overlay, react-scripts
    • babel-preset-react-app, cra-template-typescript, cra-template, create-react-app, react-dev-utils, react-error-overlay, react-scripts
    • babel-plugin-named-asset-import, confusing-browser-globals, create-react-app, react-dev-utils, react-error-overlay, react-scripts
    • babel-preset-react-app, create-react-app, react-dev-utils, react-error-overlay, react-scripts
    • babel-plugin-named-asset-import, babel-preset-react-app, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • eslint-config-react-app, react-scripts
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, cra-template-typescript, react-dev-utils, react-error-overlay, react-scripts

    Committers: 63

    Source code(tar.gz)
    Source code(zip)
  • v3.4.4(Oct 20, 2020)

    3.4.4 (2020-10-20)

    v3.4.4 release bumps resolve-url-loader to a version for which npm audit does not report a vulnerability. Note that this vulnerability did not affect Create React App projects, so this change is only necessary to satisfy auditing tools.

    Migrating from 3.4.3 to 3.4.4

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.4.2(Oct 20, 2020)

    3.4.2 (2020-08-11)

    v3.4.2 release bumps webpack-dev-server to a version for which npm audit does not report a vulnerability. Note that this vulnerability did not affect Create React App projects, so this change is only necessary to satisfy auditing tools.

    Migrating from 3.4.1 to 3.4.2

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.4.3(Oct 20, 2020)

    3.4.3 (2020-08-12)

    v3.4.3 release bumps terser-webpack-plugin to a version for which npm audit does not report a vulnerability. Note that this vulnerability did not affect Create React App projects, so this change is only necessary to satisfy auditing tools.

    Migrating from 3.4.2 to 3.4.3

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.4.1(Mar 21, 2020)

    3.4.1 (2020-03-20)

    v3.4.1 is a maintenance release that includes minor bug fixes and documentation updates including upgrading Babel to fix a bug in the 7.8 release line. This release also brings support for TypeScript 3.8.

    :bug: Bug Fix

    • react-scripts
    • babel-preset-react-app
    • cra-template, eslint-config-react-app, react-scripts
      • #7790 Widen eslint-config-react-app peer dependency versions (@lukyth)

    :nail_care: Enhancement

    • cra-template-typescript, cra-template
    • react-scripts

    :memo: Documentation

    • Other
      • #8515 Fix proxying API request docs (@hjr3)
      • #8561 Indicate that the file structure is the template's (@Vinnl)
    • react-scripts

    :hammer: Underlying Tools

    • babel-preset-react-app, create-react-app, react-dev-utils, react-error-overlay, react-scripts
    • react-scripts

    Committers: 9

    Migrating from 3.4.0 to 3.4.1

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.4.0(Feb 14, 2020)

    3.4.0 (2020-02-14)

    v3.4.0 is a minor release that adds new features, including support for SSL and setting PUBLIC_URL in development. It also includes a fix for Hot Module Reloading with CSS Modules as well as other bug fixes.

    :bug: Bug Fix

    • react-scripts
      • #8378 Downgrade style-loader to v0.23.1 due to CSS modules hot reload not working with v1.0.0 and above (@chybisov)
    • create-react-app, react-dev-utils, react-error-overlay
    • react-dev-utils
    • cra-template-typescript, cra-template
    • cra-template-typescript

    :nail_care: Enhancement

    • react-dev-utils, react-scripts
    • cra-template-typescript
    • cra-template-typescript, cra-template
    • react-scripts
      • #5845 Add option to provide custom ssl certificates during development (@alexbrazier)

    :memo: Documentation

    • cra-template-typescript, cra-template, react-dev-utils, react-error-overlay, react-scripts
    • Other

    :hammer: Underlying Tools

    Committers: 18

    Migrating from 3.3.1 to 3.4.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.3.1(Jan 31, 2020)

    3.3.1 (2020-01-31)

    v3.3.1 is a maintenance release that includes minor bug fixes and documentation updates.

    :bug: Bug Fix

    :nail_care: Enhancement

    • react-error-overlay
    • cra-template-typescript
    • cra-template-typescript, cra-template, react-scripts
    • create-react-app
    • cra-template-typescript, cra-template
    • eslint-config-react-app
      • #7803 Remove error for @typescript-eslint/no-namespace (@szhu)

    :memo: Documentation

    :house: Internal

    :hammer: Underlying Tools

    • babel-preset-react-app, create-react-app, react-dev-utils, react-error-overlay, react-scripts
    • react-dev-utils
    • babel-plugin-named-asset-import
    • create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • create-react-app, react-dev-utils, react-error-overlay
    • react-error-overlay, react-scripts
      • #8102 [Security] Update terser webpack plugin (@RDIL)

    Committers: 29

    Migrating from 3.3.0 to 3.3.1

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.3.0(Dec 5, 2019)

    3.3.0 (2019-12-04)

    v3.3.0 is a minor release that adds new features, including custom templates and support for the new optional chaining and nullish coalescing operators.

    Custom Templates

    You can now create a new app using custom templates.

    We've published our existing templates as cra-template and cra-template-typescript, but we expect to see many great templates from the community over the coming weeks.

    The below command shows how you can create a new app with cra-template-typescript.

    npx create-react-app my-app --template typescript
    

    Note that you can omit the prefix cra-template- when specifying which template you would like. For TypeScript users, we're deprecating --typescript in favour of --template typescript.

    If you don't set a template, we'll create your new app with cra-template - which is just a new name for our base template.

    Optional Chaining and Nullish Coalescing Operators

    We now support the optional chaining and nullish coalescing operators!

    // Optional chaining
    a?.(); // undefined if `a` is null/undefined
    b?.c; // undefined if `b` is null/undefined
    
    // Nullish coalescing
    undefined ?? 'some other default'; // result: 'some other default'
    null ?? 'some other default'; // result: 'some other default'
    '' ?? 'some other default'; // result: ''
    0 ?? 300; // result: 0
    false ?? true; // result: false
    

    If you're using TypeScript, you will need to upgrade your typescript dependency to 3.7.0 or later if you wish to use the new operators.

    If you're using Visual Studio Code 1.40 (the latest as of this release) or earlier, you will need to configure your editor if you want it to understand the new operators.

    If you're using TypeScript in your project and have already upgrade its version as described above, then you can configure VS Code to Use Workspace Version of TypeScript. If your project isn't using TypeScript, you can use the JavaScript and TypeScript Nightly extension until VS Code releases a newer version including TypeScript 3.7.0 or newer.

    Numeric Separators

    We've added support for numeric separators to improve readability of numeric literals.

    1000000000; // Is this a billion? a hundred millions? Ten millions?
    101475938.38; // what scale is this? what power of 10?
    
    1_000_000_000; // Ah, so a billion
    101_475_938.38; // And this is hundreds of millions
    

    no-unexpected-multiline

    We've removed this rule as it is not compatible with Prettier. If you rely on this rule you can re-enable it by extending our ESLint config and adding the following:

    {
      "extends": "react-app",
      "rules": {
        "no-unexpected-multiline": "warn"
      }
    }
    

    :rocket: New Feature

    • babel-preset-react-app
      • #7438 Add optional chaining and nullish coalescing operators support (@renatoagds)
    • babel-preset-react-app, react-dev-utils
    • cra-template-typescript, cra-template, create-react-app, react-scripts

    :boom: Breaking Change

    • create-react-app, react-dev-utils, react-scripts

      • #7988 Bump webpack-dev-server (@ianschmitz)

        NOTE: This is only a breaking change if you're using react-dev-utils outside of Create React App.

    :bug: Bug Fix

    • eslint-config-react-app
    • create-react-app
      • #7991 Support templates in scoped packages (@klasbj)
      • #7839 added check for typescript template and unsupported node version (@awaseem)
    • react-scripts
    • react-dev-utils

    :nail_care: Enhancement

    • cra-template-typescript, cra-template
    • react-scripts
    • cra-template
      • #7931 No spinning React logo if prefers-reduced-motion (@donavon)
    • create-react-app, react-error-overlay
    • babel-preset-react-app
      • #7726 Add babel runtime version to transform-runtime plugin to reduce bundle size (@topaxi)

    :memo: Documentation

    :house: Internal

    • react-scripts
    • Other
    • eslint-config-react-app
      • #8003 Use @typescript-eslint/no-unused-expressions to support optional chaining (@maxdavidson)
    • create-react-app
      • #7844 added e2e test for checking typescript template with unsupported node (@awaseem)
      • #7882 refactor: remove double coerce (@mrmckeb)
      • #7880 Pass through fully specified template name (@iansu)
    • cra-template-typescript
      • #7944 Make base and TypeScript templates consistent (@suprj)
    • create-react-app, react-dev-utils, react-scripts

    :hammer: Underlying Tools

    • babel-preset-react-app, cra-template-typescript, cra-template, create-react-app, react-dev-utils, react-error-overlay, react-scripts
    • create-react-app, react-dev-utils, react-scripts
    • react-app-polyfill
    • babel-preset-react-app, react-app-polyfill, react-dev-utils, react-scripts
    • react-scripts
    • babel-preset-react-app, cra-template-typescript, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • react-dev-utils
    • babel-plugin-named-asset-import, babel-preset-react-app, react-error-overlay, react-scripts
    • react-error-overlay, react-scripts

    Committers: 42

    Migrating from 3.2.0 to 3.3.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.2.0(Oct 3, 2019)

    3.2.0 (2019-10-03)

    v3.2.0 is a minor release that adds support for production profiling and ignoring TypeScript type errors to make migrating JavaScript projects to TypeScript easier. It also includes other minor bug fixes and documentation updates.

    :rocket: New Feature

    • react-scripts
    • react-dev-utils, react-scripts

    :bug: Bug Fix

    • react-scripts
    • react-app-polyfill
      • #7205 Guard polyfills against window possibly being undefined (@jxom)

    :nail_care: Enhancement

    • react-scripts
    • react-dev-utils

    :memo: Documentation

    • #7302 docs: note that 2 to 3 migration may require deletion of node_modules (@kimpers)
    • #7757 Documentation typo fix: accessbile→accessible (@tomer)
    • #7601 [Documentation] Updated list of supported Jest config overrides (@neilbryson)
    • #7705 Update runtime chunk name separator in docs (@samuelmeuli)

    :house: Internal

    • react-scripts
    • react-dev-utils, react-scripts

    :hammer: Underlying Tools

    Committers: 19

    Migrating from 3.1.2 to 3.2.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.1.2(Sep 19, 2019)

    3.1.2 (2019-09-19)

    v3.1.2 is a maintenance release that includes minor bug fixes and documentation updates.

    :bug: Bug Fix

    • react-scripts
    • babel-preset-react-app, react-error-overlay, react-scripts

    :nail_care: Enhancement

    :memo: Documentation

    :house: Internal

    :hammer: Underlying Tools

    • babel-plugin-named-asset-import, confusing-browser-globals, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • react-scripts
    • eslint-config-react-app, react-scripts

    Committers: 20

    Migrating from 3.1.1 to 3.1.2

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.1.1(Aug 13, 2019)

    3.1.1 (2019-08-13)

    v3.1.1 is a maintenance release that includes minor bug fixes and documentation updates.

    :bug: Bug Fix

    :nail_care: Enhancement

    • eslint-config-react-app

    :memo: Documentation

    Committers: 3

    Migrating from 3.1.0 to 3.1.1

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.1.0(Aug 9, 2019)

    3.1.0 (2019-08-09)

    v3.1.0 is a minor release that adds ESLint 6 support as well as experimental support for extending and customizing the ESLint config along with other minor bug fixes and documentation updates.

    Highlights

    • ESLint 6: #7415
    • Experimental ESLint config customization: #7036
    • More Jest config options: #6055
    • Option to configure or disable image inlining: #6060

    :rocket: New Feature

    • eslint-config-react-app, react-error-overlay, react-scripts
    • eslint-config-react-app, react-scripts
    • react-dev-utils
    • react-scripts

    :boom: Breaking Change

    • react-scripts
    • eslint-config-react-app, react-error-overlay, react-scripts

    :bug: Bug Fix

    • react-dev-utils
      • #7444 Fix for #6720: HMR not working in Firefox if proxy option present (@dmile)
    • react-scripts
    • eslint-config-react-app
    • react-error-overlay, react-scripts
      • #7257 Upgrade webpack to 4.35.0 to fix dynamic import issue (@iansu)

    :nail_care: Enhancement

    :memo: Documentation

    :house: Internal

    :hammer: Underlying Tools

    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • eslint-config-react-app, react-error-overlay, react-scripts
    • eslint-config-react-app, react-scripts
    • react-scripts
    • react-dev-utils

    Committers: 46

    Migrating from 3.0.1 to 3.1.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.0.1(May 8, 2019)

    3.0.1 (2019-05-08)

    v3.0.1 is a maintenance release that adjusts some ESLint rules for TypeScript along with other minor bug fixes and documentation updates.

    :boom: Breaking Change

    • babel-preset-react-app
      • #6887 Update dependencies of Babel preset with recent changes (@skoging)

    :bug: Bug Fix

    • react-error-overlay, react-scripts
    • eslint-config-react-app
    • eslint-config-react-app, react-scripts
    • react-dev-utils
      • #6876 Change cssmodule classname hash to use relative paths (@vg-stan)

    :nail_care: Enhancement

    • react-dev-utils, react-scripts
    • babel-preset-react-app
      • #6887 Update dependencies of Babel preset with recent changes (@skoging)
    • react-scripts
      • #6706 Generate SVG component name in Jest fileTransform (@dallonf)
      • #6300 Remove body padding reset from templates (@Hurtak)

    :memo: Documentation

    :house: Internal

    • react-scripts
      • #6854 Remove Object.assign from MiniCssExtractPlugin options (@swashcap)

    Committers: 12

    Migrating from 3.0.0 to 3.0.1

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v3.0.0(Apr 22, 2019)

    3.0.0 (April 22, 2019)

    Create React App 3.0 brings some exciting new features including support for Hooks!

    Thanks to all the maintainers and contributors who worked so hard on this release! :tada:

    Highlights

    • Jest 24: #6278
    • Hooks support: #5997
    • TypeScript linting: #6513
    • browserslist support in @babel/preset-env: #6608
    • Absolute imports using jsconfig.json/tsconfig.json: #6656

    Migrating from 2.1.x to 3.0.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    

    If you previously ejected but now want to upgrade, one common solution is to find the commits where you ejected (and any subsequent commits changing the configuration), revert them, upgrade, and later optionally eject again. It’s also possible that the feature you ejected for is now supported out of the box.

    Breaking Changes

    Like any major release, [email protected] contains a few breaking changes. We expect that they won't affect every user, but we recommend you look over this section to see if something is relevant to you. If we missed something, please file a new issue.

    Jest 24

    We've updated from Jest 23 to get the latest improvements in Jest 24. We've noticed some differences in snapshot serialization in Jest 24, so you may need to adjust your tests slightly once you update. You can read more about what's changed in the Jest 24 blog post.

    Hooks support

    We now enforce Rules of Hooks with eslint-plugin-react-hooks. If you are breaking any of the rules of Hooks this will cause your build to fail.

    TypeScript linting

    We now lint TypeScript files. You can see the list of rules we enforce to check if your project is compatible. If you're using Visual Studio Code you can follow our guide to setup up your editor to display lint warnings.

    browserslist support in @babel/preset-env

    The browserslist config in your package.json is now used to control the output of your JavaScript files. You can use separate configuration for development and production. See here for a good starting point which gives a good development experience, especially when using language features such as async/await, but still provides high compatibility with many browsers in production

    Remove --no-watch flag

    We've removed the --no-watch flag from the start script in favor of Jest's own --watchAll=false.

    New structure in asset-manifest.json

    All asset paths have been moved under the files key in asset-manifest.json.

    New Features

    using jsconfig.json/tsconfig.json

    We now support setting baseUrl in jsconfig.json and tsconfig.json. To configure baseUrl to point to the src directory in your JavaScript project, create a jsconfig.json file in your project root:

    ```json
    {
      "compilerOptions": {
        "baseUrl": "src"
      },
      "include": ["src"]
    }
    ```
    

    If you have a TypeScript project you can configure baseUrl the same way in your tsconfig.json.

    Currently the only supported options for baseUrl are node_modules (the default) and src.

    PostCSS Normalize

    You can now include a version of Normalize.css in your project that will use your browserslist setting to generate the appropriate styles for your target browsers. To include it simply add @import-normalize at the top of one of your CSS files.

    Detailed Changelog

    :rocket: New Feature

    • react-scripts
    • babel-plugin-named-asset-import, confusing-browser-globals, react-dev-utils, react-error-overlay, react-scripts
    • eslint-config-react-app, react-scripts
    • babel-preset-react-app, eslint-config-react-app, react-scripts
    • babel-preset-react-app, react-dev-utils, react-scripts

    :boom: Breaking Change

    • react-scripts
    • babel-preset-react-app, react-app-polyfill
    • babel-plugin-named-asset-import, confusing-browser-globals, react-dev-utils, react-error-overlay, react-scripts
    • eslint-config-react-app, react-scripts
    • babel-preset-react-app, eslint-config-react-app, react-scripts
    • babel-preset-react-app, react-dev-utils, react-scripts

    :bug: Bug Fix

    :nail_care: Enhancement

    • react-scripts
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, eslint-config-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • babel-preset-react-app, react-app-polyfill
    • create-react-app
    • react-dev-utils

    :memo: Documentation

    :house: Internal

    • Other
    • react-scripts
      • #6313 Update testMatch to also be compatible with Jest 24 (@ngbrown)
      • #4176 Remove --coverage + --watch workaround for the test command (@stipsan)
      • #6655 Change app component declaration from arrow function to regular function (@iansu)
      • #6625 change named import into default import (@xiaoxiangmoe)
      • #6621 make compiler a const not a let (@Primajin)
    • babel-plugin-named-asset-import, confusing-browser-globals, react-dev-utils, react-error-overlay, react-scripts
    • react-dev-utils
    • eslint-config-react-app
      • #6662 Sync version of babel-eslint in eslint-config-react-app for react-scripts V3 (@dalcib)

    :hammer: Underlying Tools

    • react-scripts
    • babel-plugin-named-asset-import, babel-preset-react-app, confusing-browser-globals, create-react-app, eslint-config-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts
    • babel-preset-react-app
    • babel-preset-react-app, react-dev-utils, react-error-overlay, react-scripts
    • react-dev-utils
      • #6739 Update fork-ts-checker-webpack-plugin out of alpha (@pelotom)
    • eslint-config-react-app
      • #6701 Remove project property from @typescript-eslint/parser options (@jackwilsdon)
    • eslint-config-react-app, react-scripts
      • #6653 Unpin eslint-config-react-hooks dependency (@iansu)
    • babel-preset-react-app, eslint-config-react-app, react-scripts
    • babel-preset-react-app, create-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts

    Committers: 49

    Source code(tar.gz)
    Source code(zip)
  • v2.1.8(Mar 7, 2019)

  • v2.1.7(Mar 7, 2019)

    2.1.7 (March 7, 2019)

    v2.1.7 is a maintenance release that temporarily reverts the TypeScript speed improvements (#6406) to fix a dependency issue in react-dev-utils.

    Migrating from 2.1.6 to 2.1.7

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v2.1.6(Mar 6, 2019)

    2.1.6 (March 6, 2019)

    v2.1.6 is a maintenance release that brings a few new improvements, most notably:

    • :rocket: Reduced TypeScript rebuild times while running the development server. This was previously introduced in v2.1.4 but had to be reverted. Thanks to @ianschmitz for getting this ready.

    :bug: Bug Fix

    :nail_care: Enhancement

    • react-dev-utils, react-scripts
    • create-react-app
      • #6253 Only use yarn.lock.cached if using the default Yarn registry. (@hangryCat)
    • react-scripts

    :memo: Documentation

    :house: Internal

    :hammer: Underlying Tools

    • react-scripts
      • #6387 Use contenthash instead of chunkhash for better long-term caching. (@ianschmitz)
    • Other

    Committers: 15

    Migrating from 2.1.5 to 2.1.6

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v2.1.5(Feb 11, 2019)

  • v2.1.4(Feb 10, 2019)

    2.1.4 (February 10, 2019)

    v2.1.4 is a maintenance release that brings a number of awesome improvements. A few notable ones include:

    • :rocket: Reduced TypeScript rebuild times while running the development server. TypeScript is now blazing fast! Special thanks to @deftomat and @johnnyreilly and the other contributors for their hard work on this. (#5903)
    • Jest type ahead support which provides a much nicer experience when filtering your tests using the Jest CLI (#5213)
    • And many more improvements!

    :bug: Bug Fix

    :nail_care: Enhancement

    :memo: Documentation

    :house: Internal

    • Other
    • react-scripts
    • react-dev-utils, react-scripts
    • babel-plugin-named-asset-import, react-scripts
    • react-dev-utils
    • babel-preset-react-app, react-app-polyfill, react-dev-utils, react-error-overlay, react-scripts

    :hammer: Underlying Tools

    • babel-preset-react-app, react-app-polyfill, react-dev-utils, react-scripts
    • babel-preset-react-app
    • eslint-config-react-app, react-scripts
      • #6132 Bump eslint-plugin-react version and update webpack config. (@ianschmitz)

    Committers: 29

    Migrating from 2.1.3 to 2.1.4

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v2.1.3(Jan 4, 2019)

    2.1.3 (January 4, 2019)

    v2.1.3 is a maintenance release to fix a vulnerability in webpack-dev-server.

    :memo: Documentation

    :house: Internal

    :hammer: Underlying Tools

    • react-scripts
      • #6064 Update webpack-dev-server 3.1.9 -> 3.1.14. (@Friss)

    Committers: 8

    Migrating from 2.1.2 to 2.1.3

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v2.1.2(Dec 23, 2018)

    2.1.2 (December 23, 2018)

    v2.1.2 is a maintenance release including various bug fixes.

    :rocket: New Feature

    • babel-preset-react-app
      • #5487 Add allowESModules option to babel-preset-react-app (@Pajn)

    :bug: Bug Fix

    • create-react-app
    • babel-preset-react-app
    • babel-plugin-named-asset-import
      • #5573 Fix named-asset-import plugin to work with export-as syntax (@NShahri)
    • react-app-polyfill
    • react-scripts

    :nail_care: Enhancement

    :memo: Documentation

    :house: Internal

    • react-scripts
    • Other
    • react-dev-utils
    • react-error-overlay
      • #5451 fix: add sideEffects: false to react-error-overlay. (@SimenB)
    • babel-preset-react-app
      • #5487 Add allowESModules option to babel-preset-react-app. (@Pajn)
    • create-react-app

    Committers: 36

    Migrating from 2.1.1 to 2.1.2

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v2.1.1(Nov 1, 2018)

    2.1.1 (October 31, 2018)

    Happy Halloween 🎃 👻! This spooky release brings a treat: decorator support in TypeScript files!

    :bug: Bug Fix

    • babel-preset-react-app
    • react-scripts

    :nail_care: Enhancement

    • babel-preset-react-app

    :memo: Documentation

    :house: Internal

    • react-error-overlay
    • babel-plugin-named-asset-import
    • react-scripts
      • #5651 Make serviceWorker config argument optional in typescript. (@eddedd88)

    Committers: 8

    Migrating from 2.1.0 to 2.1.1

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v2.1.0(Oct 30, 2018)

    2.1.0 (October 29, 2018)

    Create React App 2.1 adds support for TypeScript! Read the documentation to get started.

    New applications can be created using TypeScript by running:

    $ npx create-react-app my-app --typescript
    

    :rocket: New Feature

    • create-react-app, react-scripts
    • babel-preset-react-app, react-scripts

    :bug: Bug Fix

    :nail_care: Enhancement

    • create-react-app, react-scripts
      • #5593 Refine how TypeScript types are handled. (@Timer)
    • react-scripts
    • react-dev-utils, react-scripts

    :memo: Documentation

    :house: Internal

    Committers: 15

    Migrating from 2.0.5 to 2.1.0

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v2.0.5(Oct 14, 2018)

    2.0.5 (October 14, 2018)

    :bug: Bug Fix

    • react-dev-utils

    • create-react-app

      • #5362 Fix CI: non-semver compliant Yarn versions. (@Timer)
    • react-scripts

      • #5301 Fix TypeError when registering service workers without config. (@peterbe)

    :nail_care: Enhancement

    • babel-preset-react-app

      • #4984 Use the correct dependency for babel-plugin-dynamic-import-node. (@vikr01)
    • react-scripts

    :memo: Documentation

    :house: Internal

    • Other

    • create-react-app

      • #5362 Fix CI: non-semver compliant Yarn versions. (@Timer)
    • react-scripts

      • #5317 Remove unused require for getCacheIdentifier after ejecting. (@benbrandt)

    Committers: 23

    Migrating from 2.0.4 to 2.0.5

    Inside any created project that has not been ejected, run:

    npm install --save --save-exact [email protected]
    

    or

    yarn add --exact [email protected]
    
    Source code(tar.gz)
    Source code(zip)
  • v2.0.4(Oct 3, 2018)

    2.0.4 (October 3, 2018)

    :bug: Bug Fix

    • react-scripts
    • babel-preset-react-app

    :nail_care: Enhancement

    • create-react-app
    • react-scripts

    :memo: Documentation

    :house: Internal

    Committers: 11

    Source code(tar.gz)
    Source code(zip)
Owner
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Facebook
binomialpool.finance is an unruggable liquidity pool, running on Binance Smart Chain.

binomialpool.finance is an unruggable liquidity pool, running on Binance Smart Chain. Unruggable means that the system remains secure even if the core

null 48 Mar 3, 2022
NextJS Starter Example for Running Zesty.io CMS

Zesty.io + NextJS Getting Started Node and NPM need to be installed. From your command line.

Zesty.io 9 Dec 8, 2022
DEPRECATED - A front-end template that helps you build fast, modern mobile web apps.

Deprecation Note Mobile Boilerplate is no longer maintained. Please use HTML5 Boilerplate as a decent starting point for your project. Mobile Boilerpl

H5BP 3.9k Dec 14, 2022
This project is for backend developers with node js. It create the "Mongoose models, routers and controllers" with cli command line.

Node.js Boilerplate This project is for backend developers with node js. It create the "Mongoose models, routers and controllers" with cli command lin

Bilal Yaver 3 Sep 19, 2022
Jekyllist - Modern Boilerplate on Jekyll

Jekyllist - Modern Boilerplate on Jekyll Jekyllist is a production ready boilerplate for humans who wants to build simple websites (portfolio sites, b

Atakan Oz 2 Jul 21, 2022
React Starter Kit — isomorphic web app boilerplate (Node.js, Express, GraphQL, React.js, Babel, PostCSS, Webpack, Browsersync)

React Starter Kit — "isomorphic" web app boilerplate React Starter Kit is an opinionated boilerplate for web development built on top of Node.js, Expr

Kriasoft 21.7k Jan 1, 2023
An experiment in building a public facing personal knowledge web app with TiddlyWiki and Nodejs.

Maarfapad What is this? Maarfapad was my attempt at learning Expressjs back in 2016 while building a CRUD app to handle TiddlyWiki html files. It was

A.B. Samma 3 Mar 12, 2022
Webplate is an awesome front-end framework that lets you stay focused on building your site or app all the while remaining really easy to use.

Webplate Framework Webplate is an awesome front-end framework that lets you stay focused on building your site or app all the while remaining really e

Chris Humboldt 560 Nov 24, 2022
React + Redux starter kit / boilerplate with Babel, hot reloading, testing, linting and a working example app built in

A comprehensive starter kit for rapid application development using React. Why Slingshot? One command to get started - Type npm start to start develop

Cory House 9.8k Jan 3, 2023
Starting a new JS app? Build, test and run advanced apps with kyt 🔥

kyt Every sizable JavaScript web app needs a common foundation: a setup to build, run, test and lint your code. kyt is a toolkit that encapsulates and

The New York Times 1.9k Dec 26, 2022
一個透過Google App Script發送台科公佈欄資訊的機器人

GAS-NTUST-bulletin 一個透過Google App Script發送台科公佈欄資訊到telegram和line notify的機器人 機器人網址 Telegram Line Screenshots 部署說明 先把學校的信件設定轉寄到某個gmail,,然後把GAS跑在該帳號上 基本上把

null 23 Nov 17, 2022
Hi there! This is a react native starter which used to build a awesome Event Booking App based on the Figma design. You can download or clone it to speed up your projects.

mcrn-event-booking-app-starter Hi there! This is a react native starter which used to build a awesome Event Booking App based on the Figma design. You

Roy Chen 43 Dec 19, 2022
A cli tool to generate cra-template from current create-react-app project.

Create Cra Template A cli tool to generate cra-template from current create-react-app project. Create Cra Template Templates cra-template-popular cra-

Yoki 23 Aug 18, 2022
An embedded app starter template with all the required stuff hooked up.

Shopify Node.js x Express.js x React.js Boilerplate An embedded app starter template to get up and ready with Shopify app development with JavaScript.

Harshdeep Singh Hura 124 Dec 25, 2022
An embedded app starter template with all the required stuff hooked up.

Shopify Node.js x Express.js x React.js Boilerplate An embedded app starter template to get up and ready with Shopify app development with JavaScript.

Harshdeep Singh Hura 47 May 25, 2022
A professional front-end template for building fast, robust, and adaptable web apps or sites.

HTML5 Boilerplate HTML5 Boilerplate is a professional front-end template for building fast, robust, and adaptable web apps or sites. This project is t

H5BP 53.8k Dec 28, 2022
An upgradable boilerplate for Progressive web applications (PWA) with server side rendering, build with SEO in mind and achieving max page speed and optimized user experience.

React PWA v2 A highly scalable, Progressive Web Application foundation,boilerplate, with the best Developer Experience. Demo: https://demo.reactpwa.co

Atyantik 2.5k Dec 26, 2022
An example of a mobile-first responsive web design

Mobile-First-RWD This demo is an example of a mobile-first responsive web design. This is a companion demo to the tutorial I wrote on HTML5 Rocks and

Brad Frost 68 Sep 24, 2022
A boilerplate for Node.js web applications

Hackathon Starter Live Demo: https://hackathon-starter.walcony.com Jump to What's new? A boilerplate for Node.js web applications. If you have attende

Sahat Yalkabov 34k Dec 28, 2022