-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eslint config & plugin packages - prep for monorepo RFC #34581
Conversation
cc @cortinico Monorepo PR |
There are some errors from CircleCI about the new packages not being in NPM yet they are referenced as dependencies in the old packages. If you'd like, I can split this up so the new packages are published first, then land that, and make a 2nd PR to update the old packages, making them point to the new ones. I didn't do that initially because I know this is going to cause a lot of internal work, and I thought 2 PRs might increase that workload. |
Base commit: e680018 |
Base commit: e680018 |
cc @cipolleschi for tracking |
Hey @afoxman I've posted an update on the Monorepo effort here: I'm not entirely sure how we want to handle this (@kelset has a stronger opinion I believe). I believe we probably don't want to keep wrapper packages for the older package names (it would be quite of an overkill, as we'll have to do it for all the packages). I would suggest we downscale the PR to just renaming + bumping the packages. |
Hi @hoxyq, definitely! Thank you for picking this up for me and pushing the monorepo forward. |
@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Summary: The [monorepo RFC](react-native-community/discussions-and-proposals#480) calls for renaming: * `react-native-community/eslint-config` -> `react-native/eslint-config` * `react-native-community/eslint-plugin` -> `react-native/eslint-plugin` It also calls for the versions to be aligned with the rest of main -- currently `0.71.0`. ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> General Added - Added a new package `react-native/eslint-config` and migrated ESLint configuration into it from `react-native-community/eslint-config` General Added - Added a new package `react-native/eslint-plugin` and migrated ESLint plugins into it from `react-native-community/eslint-plugin` General Changed - Migrated contents of `react-native-community/eslint-config` into `react-native/eslint-config` General Changed - Migrated contents of `react-native-community/eslint-plugin` into `react-native/eslint-plugin` Pull Request resolved: facebook#34581 Test Plan: First test is to run `yarn lint`, and verify that output matches before and after this change. Second test is to change the ESLint config to use the "old" packages (under `react-native-commnuity`) and run `yarn lint` to make sure that they work as expected. This is what customers will experience, until they manually move to the new ESLint packages. Differential Revision: D41495332 Pulled By: hoxyq fbshipit-source-id: 36e756333ab0711927927c18af736c0931dbf9b4
977a213
to
7972310
Compare
PR build artifact for 7972310 is ready. |
PR build artifact for 7972310 is ready. |
@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
PR build artifact for c657aad is ready. |
PR build artifact for c657aad is ready. |
…ch the rest of the repo.
PR build artifact for 2915e79 is ready. |
PR build artifact for 2915e79 is ready. |
@hoxyq has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
This pull request was successfully merged by @afoxman in 5aead70. When will my fix make it into a release? | Upcoming Releases |
Its not working:
|
@mm-webx I don't think it's expected to work yet, these new versions still need to be published. It will take time, for now you are not supposed to migrate to it. (0.71 will not use these new versions) |
Hey @mm-webx, @kelset is correct, before we publish this package you can use |
Summary: The [monorepo RFC](react-native-community/discussions-and-proposals#480) calls for renaming: * `react-native-community/eslint-config` -> `react-native/eslint-config` * `react-native-community/eslint-plugin` -> `react-native/eslint-plugin` It also calls for the versions to be aligned with the rest of main -- currently `0.72.0`. ## Changelog <!-- Help reviewers and the release process by writing your own changelog entry. For an example, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [General][Changed] - Renamed `react-native-community/eslint-config` to `react-native/eslint-config` v0.72.0 to align with other packages [General][Changed] - Renamed `react-native-community/eslint-plugin` to `react-native/eslint-plugin` v0.72.0 to align with other packages Pull Request resolved: facebook#34581 Test Plan: First test is to run `yarn lint`, and verify that output matches before and after this change. Second test is to change the ESLint config to use the "old" packages (under `react-native-commnuity`) and run `yarn lint` to make sure that they work as expected. This is what customers will experience, until they manually move to the new ESLint packages. Reviewed By: cortinico Differential Revision: D41520500 Pulled By: hoxyq fbshipit-source-id: a61e5ae15d5aaf11f0143a3b0257a60a03b1550b
### Summary Fixes #443 Replaced `@react-native-community/eslint-config` with `@react-native/eslint-config`. Please see the PR that changes the name on the React Native repository [here](facebook/react-native#34581) ### Test plan 1. Create a new React Native library 2. cd into the library you have created. 3. run `yarn lint` 4. Make sure linting works properly.
Summary
The monorepo RFC calls for renaming:
@react-native-community/eslint-config
->@react-native/eslint-config
@react-native-community/eslint-plugin
->@react-native/eslint-plugin
It also calls for the versions to be aligned with the rest of main -- currently
0.72.0
.Changelog
[General][Changed] - Renamed
@react-native-community/eslint-config
to@react-native/eslint-config
v0.72.0 to align with other packages[General][Changed] - Renamed
@react-native-community/eslint-plugin
to@react-native/eslint-plugin
v0.72.0 to align with other packagesTest Plan
First test is to run
yarn lint
, and verify that output matches before and after this change.Second test is to change the ESLint config to use the "old" packages (under
@react-native-commnuity
) and runyarn lint
to make sure that they work as expected. This is what customers will experience, until they manually move to the new ESLint packages.