This project is a fork of create-react-app-typescript further tailored to the opinionated needs of @majodev and all about apps.
- Fully configured Visual Studio code environment (debugging, recommended extensions, tasks).
- Allows to extend webpack configuration through a
webpack.js
inside the project without the need to eject.
See the updated README for more information on the included dependencies.
See Forking react-scripts for information of the forking process.
Create React apps (with Typescript) with no build configuration.
Do you know react and want to try out typescript? Or do you know typescript and want to try out react? Get all the benefits from create-react-app
but you use typescript! 🚀
npm install -g create-react-app
create-react-app my-app --scripts-version=aaa-react-scripts-ts
cd my-app/
npm start
No configuration or complicated folder structures, just the files you need to build your app.
Once the installation is done, you can run some commands inside the project folder:
Runs the app in development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will see the build errors and lint warnings in the console.
Runs the test watcher in an interactive mode.
By default, runs tests related to files changes since the last commit.
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!
The User Guide includes information on different topics, such as:
- Updating to New Releases
- Folder Structure
- Available Scripts
- Supported Language Features and Polyfills
- Syntax Highlighting in the Editor
- Displaying Lint Output in the Editor
- Debugging in the Editor
- Changing the Page
<title>
- Installing a Dependency
- Importing a Component
- Adding a Stylesheet
- Post-Processing CSS
- Adding a CSS Preprocessor (Sass, Less etc.)
- Adding Images and Fonts
- Using the
public
Folder - Using Global Variables
- Adding Bootstrap
- Adding Flow
- Adding Custom Environment Variables
- Can I Use Decorators?
- Integrating with an API Backend
- Proxying API Requests in Development
- Using HTTPS in Development
- Generating Dynamic
<meta>
Tags on the Server - Pre-Rendering into Static HTML Files
- Running Tests
- Developing Components in Isolation
- Making a Progressive Web App
- Deployment
- Advanced Configuration
- Troubleshooting
A copy of the user guide will be created as README.md
in your project folder.
Please refer to the User Guide for this and other information.
-
One Dependency: There is just one build dependency. It uses Webpack, Babel, ESLint, and other amazing projects, but provides a cohesive curated experience on top of them.
-
Convention over Configuration: You don't need to configure anything by default. 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.
If you’re getting started with React, use create-react-app
to automate the build of your app. There is no configuration file, and react-scripts
is the only extra build dependency in your package.json
. Your environment will have everything you need to build a modern React app:
- React, JSX, ES6, and Flow syntax support.
- Language extras beyond ES6 like the object spread operator.
- A dev server that lints for common errors.
- Import CSS and image files directly from JavaScript.
- Autoprefixed CSS, so you don’t need
-webkit
or other prefixes. - A
build
script to bundle JS, CSS, and images for production, with sourcemaps.
The feature set is intentionally limited. It doesn’t support advanced features such as server rendering or CSS modules. The tool is also non-configurable because it is hard to provide a cohesive experience and easy updates across a set of tools when the user can tweak anything.
You don’t have to use this. Historically it has been easy to gradually adopt React. However many people create new single-page React apps from scratch every day. We’ve heard loud and clear that this process can be error-prone and tedious, especially if this is your first JavaScript build stack. This project is an attempt to figure out a good way to start developing React apps.
If you’re a power user and you aren’t happy with the default configuration, you can “eject” from the tool and use it as a boilerplate generator.
Running npm run eject
copies all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. Commands like npm start
and npm run build
will still work, but they will point to the copied scripts so you can tweak them. At this point, you’re on your own.
Note: this is a one-way operation. Once you eject
, you can’t go back!
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Some features are currently not supported:
- Server rendering.
- Some experimental syntax extensions (e.g. decorators).
- CSS Modules.
- Importing LESS or Sass directly (but you still can use them).
- Hot reloading of components.
Some of them might get added in the future if they are stable, are useful to majority of React apps, don’t conflict with existing tools, and don’t introduce additional configuration.
The tools used by Create React App are subject to change. Currently it is a thin layer on top of many amazing community projects, such as:
- webpack with webpack-dev-server, html-webpack-plugin and style-loader
- Babel with ES6 and extensions used by Facebook (JSX, object spread, class properties)
- Autoprefixer
- ESLint
- Jest
- and others.
All of them are transitive dependencies of the provided npm package.
When you run npm run build
the terminal will output the error, including the highlighted sourecode (like babel)!
- Merge facebookincubator/create-react-app@0.9.5 into react-scripts-ts
- Merge facebookincubator/create-react-app@0.9.4 into react-scripts-ts
- Merge facebookincubator/create-react-app@0.9.3 into react-scripts-ts
- Merge facebookincubator/create-react-app@0.9.2 into react-scripts-ts
- Merge facebookincubator/create-react-app@0.9.1 into react-scripts-ts
- Merge facebookincubator/create-react-app@0.9.0 into react-scripts-ts
- Add missing
cli-highlight
dependency
- Print file names when running
npm run build
- Add support for
setupTest.ts
- Highlight source code when erroring in
npm run build
- Change mentions of
eslint
totslint
- Remove hidden character from
tsconfig.json
- Copy
typescriptTransform.js
when runningnpm run eject