cheshirecode / cra-rni-monorepo

Starter kit for code-sharing between CRA and ejected CRNA

cra-rni-monorepo

Set up CRA and barebone RN in the same monorepo as a code-sharing experiment for future boilerplates. Followed the great guide at https://medium.com/viewstools/how-to-use-yarn-workspaces-with-create-react-app-and-create-react-native-app-expo-to-share-common-ea27bc4bad62 and:

• Skip Views Tools to keep this as lightweight as possible.
• Use react-native CLI to init a barebone RN setup instead of CRNA.
• Use https://github.com/viewstools/yarn-workspaces-cra-crna/blob/master/crna-make-symlinks-for-yarn-workspaces/index.js in native and remove reference to Expo to prevent breakage.

Howto

• Clone/fork the repo

git clone [email protected]:cheshirecode/cra-rni-monorepo.git
cd cra-rni-monorepo

• Run yarn once to grab all dependencies.
• Start web development build yarn start:web.
• Run the RN bundler yarn start:bundler.
• Run the RN iOS/Android simulator yarn start:ios or yarn start:android.
• Edit some files in core folder and see the magic!

Contributors

Thanks goes to these wonderful people (emoji key):

cheshireCode 💻 ⚠️

This project follows the all-contributors specification. Contributions of any kind welcome!

cra-rni-monorepo's Issues

Get Jest to work with RN app in monorepo

Automate the steps to create monorepo

All the steps have borrowed heavily from viewstools/yarn-workspaces-cra-crna#3. It would be good to refine them into a script like CRA/CRNA fashion.

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

There have been updates to the react monorepo:

• • The dependency react was updated from 16.6.1 to 16.6.2.

• The dependency react-dom was updated from 16.6.1 to 16.6.2.
• The devDependency react-test-renderer was updated from 16.6.1 to 16.6.2.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

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

The dependency react-scripts was updated from 2.1.4 to 2.1.5.

🚨 View failing branch.

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

react-scripts is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴