Release It! π
react-native-monorepo-tools
Our great sponsors
Release It! π | react-native-monorepo-tools | |
---|---|---|
9 | 4 | |
7,529 | 123 | |
2.1% | - | |
8.3 | 0.0 | |
6 days ago | over 1 year ago | |
JavaScript | JavaScript | |
MIT License | GNU General Public License v3.0 only |
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.
Release It! π
-
Nx - Highlights of 2023
Open source libraries and frameworks share a common necessity: the need to develop multiple packages cohesively and efficiently while managing their versioning and publishing to NPM. Nx has emerged as a go-to choice for handling such open source monorepos (as we'll explore further in the next section of this blog post). Until recently, one area Nx did not address directly was versioning and release management. Traditionally, this gap has been filled with tools like release-it, changesets, or custom Node scripts, similar to our approach in the Nx repository.
- automatic changelog generation with CI
-
How does the typescript-eslint project generate its changelogs?
Hi. I'm maintaining a small monorepo and I'd like to learn techniques from large, mature projects like typescript-eslint. I assume they automate changelogs from commit logs and/or PRs, but I can't figure out how they do it by looking at their source code. I do know of tools like release-it that helps automate the process; do the typescript-eslint maintainers use such a tool, or use a homegrown one?
-
Quickly start developing your own npm package library with NestJS.
This is a quick start guide for setting up a NestJS project for creating your own package library with automated versioning and package publishing. https://github.com/Emgevorgyan/nestjs-package-quick-start
-
Package Publishing Reading & Resources
Release It! - This seems promising. A CLI tool that can be used in interactive or continuous integration mode. The big appeal for me is a Yarn workspaces specific plugin.
-
Monorepo is so frustrating...
Fine, but I need a package release tool and release-it tools looks good. I install, configure and on the last step - publishing - I find out that this lib does not support monorepo... https://github.com/release-it/release-it/issues/831 and the release-it-yarn-workspaces lib does not support the latest version of release-it https://github.com/rwjblue/release-it-yarn-workspaces/issues/68
-
My ideal Rust workflow
May be less relevant for your particular workflow (because npm-specific and because everything is internal for you), but Iβm a big fan of an alternative in the auto-release-generation space: the combo of release-it and release-it-lerna-changelog, which give you the same kind of automation but donβt require specific git commit messages, because instead the combo uses the GH API and labels to generate the changelog. This is a muuuuuch nicer experience for external contributors, because it puts the responsibility for that back on maintainers instead.
-
DynamoDB GUI with Electron, React & Typescript
Release It - To create tags, bump the versions, manage release betas and detect merged changes.
-
Writing a High Quality README! π₯
Release It
react-native-monorepo-tools
-
Monorepo is so frustrating...
Second app with bare RN. Similar story. It doesn't work. I googled and found this https://github.com/mmazzarolo/react-native-monorepo-tools . But still doesn't work... I found some random example https://github.com/aws-samples/aws-sdk-js-tests/blob/main/packages/react-native/metro.config.js and wow it works. I skip the confusion with tsconfig.json, setting path etc.
-
Running React Native everywhere: The Web
Install CRACO and react-native-monorepo-tools:
-
Running React Native everywhere: Windows & macOS
Last but not least, use react-native-monorepo-tools to make metro compatible with Yarn Workspaces:
-
Running React Native everywhere: Android & iOS
To do so, install react-native-monorepo-tools, a set of utilities for making metro compatible with Yarn workspaces based on our nohoist list.
What are some alternatives?
semantic-release - :package::rocket: Fully automated version management and package publishing
metro - π The JavaScript bundler for React Native
autochecker - β»οΈ Test your libraries in many different versions of NodeJS, Ruby, Java and many other languages
react-app-rewired - Override create-react-app webpack configs without ejecting
iProxy - π Cross platform Web debugging proxyοΌfork of LightProxyγLinux & ε€η½ε‘ζ―ζοΌ
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
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.
prop-sets - Generate and test every possible instance of a component in React
create-react-app - Set up a modern web app by running one command.
lightproxy - π Cross platform Web debugging proxy
react-native-web - Cross-platform React UI packages