Rename react-aria to react-aria-nutrient

Author: ritz078

.parcelrc

@@ -10,7 +10,7 @@
     "bundle-text:*.svg": ["@parcel/transformer-svg", "@parcel/transformer-inline-string"],
     "*.{md,mdx}": ["parcel-transformer-mdx-docs"],
     "*.svg": ["@parcel/transformer-svg-react"],
-    "packages/@react-aria/example-theme/**/*.css": ["@parcel/transformer-css"],
+    "packages/@react-aria-nutrient/example-theme/**/*.css": ["@parcel/transformer-css"],
     "*.css": ["...", "parcel-transformer-css-env"],
     "*.{js,mjs,jsm,jsx,es6,cjs,ts,tsx}": [
       "@parcel/transformer-js",

.storybook/main.js

@@ -1,7 +1,6 @@
-
 module.exports = {
   stories: [
-    '../packages/@{react-aria,react-stately,spectrum-icons}/*/stories/*.stories.{js,jsx,ts,tsx}',
+    '../packages/@{react-aria-nutrient,react-stately,spectrum-icons}/*/stories/*.stories.{js,jsx,ts,tsx}',
     '../packages/@react-spectrum/!(s2)/stories/*.stories.{js,jsx,ts,tsx}',
     '../packages/react-aria-components/stories/*.stories.{js,jsx,ts,tsx}'
   ],

CONTRIBUTING.md

@@ -3,26 +3,33 @@
 Thanks for choosing to contribute! We look forward to improving web applications together. Here you will find information on how to propose bug fixes, suggest improvements, and develop locally.
 
 ## Better together
+
 We believe that the best way to build a better web is together as a community. The React Spectrum project aims to make it easier to build design systems and component libraries with high quality interactions and accessibility for all. The core team and all external contributors follow the same process in order maintain a high quality codebase.
 
 ## Code of conduct
+
 We adhere to the Adobe [code of conduct](https://github.com/adobe/react-spectrum/blob/main/CODE_OF_CONDUCT.md) and by participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
 
 ## Reporting issues
+
 ### Bugs
+
 We use [GitHub issues](https://github.com/adobe/react-spectrum/issues) to track work and log bugs. Please check existing issues before filing anything new. We do our best to respond to issues within a few days. If you would like to contribute a fix, please let us know by leaving a comment on the issue.
 
 The best way to reduce back and forth on a bug is provide a small code example exhibiting the issue along with steps to reproduce it. If you would like to work on a bugfix yourself, make sure an issue exists first.
 
 Please follow the issue templates when filing new ones and add as much information as possible.
 
 ### Feature requests
+
 Our components can always be improved upon. If you have a feature request, you can use our Feature Request issue template. For larger scopes of work, it is a good idea to open a Request For Comments (RFC) first to gather feedback from the team. Please follow our RFC [template](https://github.com/adobe/react-spectrum/blob/main/rfcs/template.md). Make a PR to add your RFC to the [rfcs folder](https://github.com/adobe/react-spectrum/tree/main/rfcs) to give the team and the community a chance to discuss the proposal.
 
 ### Security issues
+
 Security issues shouldn't be reported on this issue tracker. Instead, please follow the directions [here](https://helpx.adobe.com/security/alertus.html) to contact our security team.
 
 ## Pull Requests
+
 For significant changes, it is recommended that you first propose your solution in [an RFC](#feature-requests) and gather feedback.
 
 A few things to keep in mind before submitting a pull request:
@@ -36,6 +43,7 @@ A few things to keep in mind before submitting a pull request:
 - Remember that all submissions require review, please be patient.
 
 The team will review all pull requests and do one of the following:
+
 - request changes to it (most common)
 - merge it
 - close it with an explanation.
@@ -45,71 +53,87 @@ Read [GitHub's pull request documentation](https://help.github.com/articles/abou
 Lastly, please follow the pull request template when submitting a pull request!
 
 ### Contributor License Agreement
+
 All third-party contributions to this project must be accompanied by a signed contributor license agreement. This gives Adobe permission to redistribute your contributions as part of the project. [Sign our CLA](https://opensource.adobe.com/cla.html). You only need to submit an Adobe CLA one time, so if you have submitted one previously, you are good to go!
 
 ## Where to start
+
 There are many places to dive into react-spectrum to help out. Before you take on a feature or issue, make sure you become familiar with [our architecture](https://react-spectrum.adobe.com/architecture.html).
 
 If you are looking for place to start, consider the following options:
+
 - Look for issues tagged with help wanted and/or good first issue.
 - Help triage existing issues by investigating problems and following up on missing information.
 - Update missing or fix existing documentation
 - Review and test open pull requests
 
 ## Developing
+
 When you are ready to start developing you can clone the repo and start storybook.
 Make sure you have the following requirements installed: [node](https://nodejs.org/) (v14.15.0+) and [yarn](https://yarnpkg.com/en/) (v1.22.0+)
 
 Fork the repo first using [this guide](https://help.github.com/articles/fork-a-repo), then clone it locally.
+
 ```
 git clone https://github.com/YOUR-USERNAME/react-spectrum
 cd react-spectrum
 yarn install
 ```
 
 You can then run the storybook and browse to [http://localhost:9003](http://localhost:9003) with:
+
 ```bash
 yarn start
 ```
 
 Or run the documentation and browse to [http://localhost:1234/](http://localhost:1234/) with:
+
 ```bash
 yarn start:docs
 ```
 
 ### Component/Hook scaffolding
+
 If you are looking to contribute a brand new component or Hook in a package that does not exist yet, please run the following command.
+
 ```bash
 yarn plop
 ```
+
 This will start a series of cli prompts to determine what template files and folders should be generated to help quick start your contribution.
 The prompts are as follows:
 
 1. What type of project are you setting up?
-    - Select "React Spectrum v3"
+
+   - Select "React Spectrum v3"
 
 2. Scope name(s)
-    - Select the package scopes that make sense for your contribution (e.g. react-spectrum if you are contributing a component, react-aria for an aria Hook, etc)
+
+   - Select the package scopes that make sense for your contribution (e.g. react-spectrum if you are contributing a component, react-aria for an aria Hook, etc)
 
 3. Package name, all lowercase (e.g. textfield)
 
 4. Component name, please use appropriate uppercase (e.g. TextField)
-    - If you are contributing a non-component Hook, just enter the name of your Hook.
+
+   - If you are contributing a non-component Hook, just enter the name of your Hook.
 
 5. Component css module name, blank if N/A. If unsure, check @adobe/spectrum-css-temp/components for a module containing the desired css (e.g. textfield)
-    - If you cannot find the component CSS module name in @adobe/spectrum-css-temp/components, feel free to reach out to a team member via GitHub Issues or Discussions.
+   - If you cannot find the component CSS module name in @adobe/spectrum-css-temp/components, feel free to reach out to a team member via GitHub Issues or Discussions.
 
 Upon answering all the prompts, the appropriate package(s) should be generated and ready for modification.
 
 **Note:** With regards to the generated docs files, please feel free to remove them if you won't be contributing docs. If you are contributing docs for a new component or Hook, please submit them in a separate pull request so that we can decide when to deploy them to our docs site.
 
 ### Tests
+
 We use [jest](https://jestjs.io/) for unit tests and [react-testing-library](https://testing-library.com/docs/react-testing-library/intro) for rendering and writing assertions. Please make sure you include tests with your pull requests. Our CI will run the tests on PRs as well as the linter and type checker. You can see on each PR whether you have passed all our checks. We split the tests into 2 groups.
 
-*Visual tests*
+_Visual tests_
+
 - A Storybook story should be written for each visual state that a component can be in (based on props).
 
-*Unit tests*
+_Unit tests_
+
 - (Props) Anything that should be changed by a prop should be tested via react-testing-library.
 - (Events) Anything that should trigger an event should be tested via react-testing-library.
 
@@ -126,50 +150,65 @@ yarn jest --coverage
 ```
 
 ### Linting
+
 The code is linted with [eslint](https://eslint.org/). The linter runs whenever you run the tests, but you can also run it with
+
 ```bash
 yarn lint
 ```
 
 ### TypeScript
+
 The code for React Spectrum is written in [TypeScript](https://www.typescriptlang.org/). The type checker will usually run in your editor, but also runs when you run
+
 ```bash
 yarn lint
 ```
 
 ### Storybook
+
 We use [Storybook](https://storybooks.js.org) for local development. Run the following command to start it:
+
 ```bash
 yarn start
 ```
+
 Then, open [http://localhost:9003](http://localhost:9003) in your browser to play around with the components and test your changes.
 
 ### Documentation
+
 Our documentation should always remain up to date. When making changes to components, make sure the appropriate documentation has been updated to reflect those changes. Documentation for each component can be found in the docs folder within a component's package. Other documentation pages can be found in the [packages/dev/docs](https://github.com/adobe/react-spectrum/tree/main/packages/dev/docs) folder in the codebase.
 
 Documentation can be run locally by using
+
 ```bash
 yarn start:docs
 ```
+
 Then, open [http://localhost:1234](http://localhost:1234) in your browser.
 
 ### Verdaccio
-We use [Verdaccio](https://verdaccio.org/) to set up a private registry for our packages to test our components in our example apps. 
+
+We use [Verdaccio](https://verdaccio.org/) to set up a private registry for our packages to test our components in our example apps.
 
 To run verdaccio, first ensure that your `git status` is clean. If your computer has an Intel chip, add the line `shopt -s globstar extglob` in the `verdaccio.sh` file after line 21. Save and commit these changes under a clear message like "Do not push". If you have an Apple silicon chip, you may skip this step.
 
 Then, run the following command:
+
 ```bash
 ./scripts/verdaccio.sh
 ```
 
 Once that is finished, open up a new terminal and change your directory to the example app you would like to test. You may test it by first running the command:
+
 ```bash
 yarn install
 ```
+
 And then the appropriate command to run the development server. Check the project's `package.json` for the correct command.
 
 If you are running into issues with `yarn install` at this step, you may need to clear your yarn cache. To do this, run this following command:
+
 ```
 rm -r ~/.yarn/berry/metadata/npm
 yarn cache clean --all
@@ -209,7 +248,7 @@ It's likely that you are using a different version of Node.js. Please use Node.j
 For example:
 
 ```
-@parcel/core: packages/@react-aria/virtualizer/src/index.ts does not export 'useVirtualizer'
+@parcel/core: packages/@react-aria-nutrient/virtualizer/src/index.ts does not export 'useVirtualizer'
 ```
 
 You may have run `yarn build` before. Please run `make clean_all && yarn` to clean up the build artifacts.

Makefile

@@ -34,7 +34,7 @@ clean_dist:
 	rm -rf packages/{react-aria,react-aria-components,react-stately}/dist
 	rm -rf packages/{react-aria,react-aria-components,react-stately}/i18n
 	rm -rf packages/@adobe/react-spectrum/i18n
-	rm -rf packages/@react-aria/i18n/server
+	rm -rf packages/@react-aria-nutrient/i18n/server
 	rm -rf packages/@react-spectrum/s2/style/dist packages/@react-spectrum/s2/page.css packages/@react-spectrum/s2/icons packages/@react-spectrum/s2/illustrations
 
 clean_parcel:

bin/useLayoutEffectRule.js

@@ -15,7 +15,7 @@ module.exports = {
     return {
       ImportDeclaration(node) {
         const source = node.source.value;
-        if (source === '@react-aria/utils' || source === './useLayoutEffect' || source === './') {
+        if (source === '@react-aria-nutrient/utils' || source === './useLayoutEffect' || source === './') {
           return;
         }
         const importSpecifiers = node.specifiers.filter(specifier => specifier.type === 'ImportSpecifier');
@@ -24,7 +24,7 @@ module.exports = {
           (item) => {
             let itemName = getName(item);
             if (itemName === 'useLayoutEffect') {
-              context.report(node, 'Please use useLayoutEffect from @react-aria/utils instead.');
+              context.report(node, 'Please use useLayoutEffect from @react-aria-nutrient/utils instead.');
             }
           }
         );

eslint.config.mjs

@@ -34,7 +34,7 @@ const ERROR = 2;
 
 export default [{
     ignores: [
-        "packages/@react-aria/i18n/server",
+        "packages/@react-aria-nutrient/i18n/server",
         "packages/@spectrum-icons/color/**/*",
         "packages/@spectrum-icons/ui/**/*",
         "packages/@spectrum-icons/workflow/**/*",
@@ -462,32 +462,32 @@ export default [{
     },
 }, {
     files: [
-        "packages/@react-aria/focus/src/**/*.ts",
-        "packages/@react-aria/focus/src/**/*.tsx",
+        "packages/@react-aria-nutrient/focus/src/**/*.ts",
+        "packages/@react-aria-nutrient/focus/src/**/*.tsx",
     ],
 
     rules: {
         "no-restricted-globals": [ERROR, {
             name: "window",
-            message: "Use getOwnerWindow from @react-aria/utils instead.",
+            message: "Use getOwnerWindow from @react-aria-nutrient/utils instead.",
         }, {
             name: "document",
-            message: "Use getOwnerDocument from @react-aria/utils instead.",
+            message: "Use getOwnerDocument from @react-aria-nutrient/utils instead.",
         }],
     },
 }, {
     files: [
-        "packages/@react-aria/interactions/src/**/*.ts",
-        "packages/@react-aria/interactions/src/**/*.tsx",
+        "packages/@react-aria-nutrient/interactions/src/**/*.ts",
+        "packages/@react-aria-nutrient/interactions/src/**/*.tsx",
     ],
 
     rules: {
         "no-restricted-globals": [WARN, {
             name: "window",
-            message: "Use getOwnerWindow from @react-aria/utils instead.",
+            message: "Use getOwnerWindow from @react-aria-nutrient/utils instead.",
         }, {
             name: "document",
-            message: "Use getOwnerDocument from @react-aria/utils instead.",
+            message: "Use getOwnerDocument from @react-aria-nutrient/utils instead.",
         }],
     },
 }, {

examples/next-app-csp/next.config.js

@@ -1,4 +1,4 @@
-const localesPlugin = require('@react-aria/optimize-locales-plugin');
+const localesPlugin = require('@react-aria-nutrient/optimize-locales-plugin');
 const glob = require('glob');
 
 /** @type {import('next').NextConfig} */

examples/next-app/next.config.js

@@ -1,4 +1,4 @@
-const localesPlugin = require('@react-aria/optimize-locales-plugin');
+const localesPlugin = require('@react-aria-nutrient/optimize-locales-plugin');
 const glob = require('glob');
 
 /** @type {import('next').NextConfig} */

examples/rac-tailwind/.parcelrc

@@ -1,6 +1,6 @@
 {
   "extends": "@parcel/config-default",
-  "resolvers": ["@react-aria/parcel-resolver-optimize-locales", "@parcel/resolver-glob", "..."],
+  "resolvers": ["@react-aria-nutrient/parcel-resolver-optimize-locales", "@parcel/resolver-glob", "..."],
   "transformers": {
     "**/intl/*.json": ["parcel-transformer-intl"]
   }

examples/rac-tailwind/package.json

@@ -9,7 +9,7 @@
   },
   "dependencies": {
     "@heroicons/react": "^2.0.16",
-    "@react-aria/parcel-resolver-optimize-locales": "^1.0.0",
+    "@react-aria-nutrient/parcel-resolver-optimize-locales": "^1.0.0",
     "@tailwindcss/postcss": "^4.0.0",
     "framer-motion": "^10.12.16",
     "parcel": "^2.13.0",

examples/remix/vite.config.ts

@@ -1,7 +1,7 @@
 import { unstable_vitePlugin as remix } from "@remix-run/dev";
 import { defineConfig } from "vite";
 import tsconfigPaths from "vite-tsconfig-paths";
-import optimizeLocales from '@react-aria/optimize-locales-plugin';
+import optimizeLocales from '@react-aria-nutrient/optimize-locales-plugin';
 
 export default defineConfig({
   plugins: [

examples/rsp-cra-18/package.json

@@ -8,7 +8,7 @@
     "@adobe/react-spectrum": "latest",
     "@babel/plugin-proposal-private-property-in-object": "^7.16.7",
     "@babel/preset-react": "^7.24.1",
-    "@react-aria/dnd": "^3.6.1",
+    "@react-aria-nutrient/dnd": "^3.6.1",
     "@react-spectrum/provider": "^3.9.7",
     "@react-spectrum/toast": "^3.0.0-beta.16",
     "@spectrum-icons/illustrations": "^3.6.8",