metro
pnpm-react-native-poc
Our great sponsors
metro | pnpm-react-native-poc | |
---|---|---|
16 | 1 | |
5,041 | 4 | |
1.0% | - | |
9.4 | 0.0 | |
1 day ago | about 2 years ago | |
JavaScript | JavaScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
metro
-
Dynamic imports supported in react native
For details on the implementation you can see Evan's PR to metro here.
-
React vs React Native: How Different Are They, Really?
Some development tools for the web are similar (Chrome debugger, mostly) to those for React Native, but other aspects are very different (working with the metro bundler, using Flipper, AsyncStorage debugging, more). Some techniques developers will use are the same (breakpoints and console logging), but others are different (knowing when to restart the packager vs reinstall the app on device).
-
Setting up React Native Monorepo with Yarn Workspaces
We’re almost done with setting up the project. The last thing in the React Native app is to add watchFolders so metro knows where the linked node_modules are. The shared modules are symlinked by yarn, and since metro doesn’t follow symlinks we need to explicitly say it where the linked node_modules are.
-
Debugging RN + Expo bare using WebStorm? Would I be better off just killing myself now?
Unfortunately it is what it is... I use intellij instead of webstorm since they're the same thing basically. I spent a shitton of time figuring out how to link a local package i was creating for my app only to discover about this issue that is almost as old as react native itself. (luckily there's rnx-kit that solves the problem). Not to talk about the impossibility to have one goddamn IDE to write both typescript, java and c++. Currently i have to write ts/js in intellij, then i have to switch to android studio to write java/c++.
-
React Native Monorepo
React Native doesn't play nicely with most monorepo tools out of the box as Metro doesn't support symlinking.
-
Running React Native everywhere: The Web
Because React Native for Web is a React website, you can use front-end tools to build and run it. For example, you can build it with Webpack or Rollup instead of Metro bundler.
-
Running React Native everywhere: Android & iOS
Before we can run the app, we still need do one more thing: make metro bundler compatible with Yarn workspaces' hoisting.
Metro bundler is the JavaScript bundler currently used by React Native. One of metro's most famous limitations (and issue number #1 in its GitHub repository) is its inability to follow symlinks. Therefore, since all hoisted libraries (basically all libraries not specified in the nohoist list) are installed in mobile/node_modules as symlinks from /node_modules, metro won't be able to detect them. Additionally, because of this issue, metro won't even be able to resolve other workspaces (e.g., @my-app/app) since they're outside of the mobile directory.
-
Running React Native everywhere: Yarn Workspaces monorepo
Second, sharing code with other projects (e.g., backend code, web apps) may get complicated. Out-of-the-box, React Native's metro bundler cannot reference code outside of the project's root directory. You can configure it to do so (and we'll do it as well later on). Still, once you do it, you'll also need to ensure dependencies resolution works correctly (to avoid loading two different versions of the same library, for example); which might not be as easy as it may sound.
While it might appear that we can access all modules from the project’s root node_modules, the reality is that build processes sometimes aren't able to traverse symlinks. This problem is especially prominent in React Native apps, where both the metro bundler and the native code can't follow symlinks.
pnpm-react-native-poc
-
React Native Monorepo
However it's possible to patch metro, or use webpack as the JS bundler instead. I've been playing around with the latter approach approach today actually: https://github.com/tom-sherman/pnpm-react-native-poc
What are some alternatives?
expo-cli - Tools for creating, running, and deploying universal Expo and React Native apps
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
react-native-web - Cross-platform React UI packages
react-native-monorepo-tools - Tools and utils to support a React Native monorepo built with Yarn Workspaces
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
minimatch - a glob matcher in javascript
react-app-rewired - Override create-react-app webpack configs without ejecting
nx - Smart Monorepos · Fast CI
react-native - A framework for building native applications using React
gatsby-plugin-react-native-web - react-native-web plugin for Gatsby
react-native-universal-monorepo - React Native boilerplate supporting multiple platforms: Android, iOS, macOS, Windows, web, browser extensions, Electron.
customize-cra - Override webpack configurations for create-react-app 2.0