xkawi / create-react-app-now Goto Github PK

View Code? Open in Web Editor NEW

139.0 1.0 9.0 95 KB

Hello, create-react-app, meet Zeit's awesome now.sh service.

Home Page: https://create-react-app.now.sh

License: MIT License

HTML 33.32% CSS 11.85% JavaScript 54.83%

zeit react now create-react-app

create-react-app-now's Introduction

create-react-app-now

Deploy React.js Static Web Apps generated with facebook/create-react-app to Zeit's awesome Now.sh service.

I wrote an article about this project here: Zero Configuration Deployment for React app with Zeit Now

Important

UPDATE: create-react-app now officially recommend using "serve" to deploy your create-react-app project. The documentation can be found here: https://create-react-app.dev/docs/deployment

I personally and strongly recommend you to check out Next.js by Zeit team. That will be my personal go to choice as well when creating new React project, and deploy to now seamlessly.

Though create-react-app-now can serves as an example on how you can use create-react-app and zeit's now together.

Having said that, it is likely that I will not actively maintain this repo anymore (e.g. update the dependencies). I will still accept PR though.

Why

create-react-app-now is created using facebook/create-react-app. Although it supports deployment to github pages and heroku, it does not feel intuitive just yet, as we need to run lots of commands.

This project is specifically to solve just that, with just 1 command: npm run deploy

This is achieved by using Zeit's awesome Now.sh service. It is fast, easy, and intuitive way of deploying your React app.

How

Simply follow this step from getting started to deployment:

$ npm install -g now
$ git clone https://github.com/xkawi/create-react-app-now
$ npm install
$ npm run deploy

First command installs the now cli globally as npm package. Another (or suggested) approach is to install Now Desktop to ensure automatic updates of now cli.

Subsequent commands simply clone this repo, install necessary npm packages and deploy it to Now.

Whenever you want to deploy new changes, just run npm run deploy again to get new public link, for free! 😄

You will enjoy all the benefits that Now offers out-of-the-box: real-time and immutable deployments all within 1 command.

Note

You might see some red text appears or warnings in the log. You can safely ignore this, because your project will still be deployed successfully.

Alternatives Deployment

If you prefer something else, please refer to create-react-app documentation here.

create-react-app-now's People

Stargazers

Watchers

Forkers

goldensunliu mauricionr corderophilosophy satyaser happywanghao advence-liz shreyak22 baronrustamov

create-react-app-now's Issues

Upgrade Dependencies

Putting this down to work on later. Though if anyone would like to submit PR, feel free to do so.

upgrade micro-list to list
upgrade react-scripts to the latest version (think need to make necessary changes to file structure)

An in-range update of react-router is breaking the build 🚨

Version 4.2.0 of react-router just got published.

Branch	Build failing 🚨
Dependency	react-router
Current Version	4.1.2
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

react-router is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v4.2.0

Changes

Aug 23, 2017

Re-run Redirect on props update (#5162 by @alexilyaev)
Prevent remounts on routes with the same component in renderRoutes (#5430 by @artywhite)
Case sensitive routes (#5438 by @paustria)
Use direct imports in platform packages (#5095 by @ruiaraujo)
Add optional otherProps argument renderRoutes (#5137 by @jharris4)
Bump hoist-non-react-statics (#5347 by @roderickhsiao)
3x build speed improvements on CI (ea1212a by @timdorr)
Use Jest for testing (172dc16 by @mjackson)
Explicit error using Route outside of Router (#4939 by @eXon)
react-router-native Link improvements (#4816 by @benstepp)
aria-current on NavLink (#4708 by @JasonEtco)
Make AndroidBackButton a generic BackButton component (#5295 by @DonnieWest)
Access Link's underlying node via innerRef (#5294 by @danielberndt)
Return null from react-router-native DeepLinking if children is undefined (#5278 by @seekshiva)
Warn when using the history prop on a pre-configured Router (#5151 by @Aprillion)
Fix memory leak in ConnectedRouter during server side rendering (#5203 by @klis87)
Reorder NavLink activeClassName/className priority (#5109 by @carloluis)
Change react-native BackAndroid to BackHandler (#5093 by @SeanGroff)
Fix react-router-native StackRouter (#5071 by @kafein)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Client-side routing?

How did you fixed client-side routing? I use react-router, which works fine in development, because webpack is running a dev-server. But in production/on now/using serve, it works until I refresh the page when I'm on a route. This makes sense, because that route does not point to a file on disk. What's the best way of fixing this?

An in-range update of react-router-dom is breaking the build 🚨

Version 4.2.0 of react-router-dom just got published.

Branch	Build failing 🚨
Dependency	react-router-dom
Current Version	4.1.2
Type	dependency