chore: rename react-aria to "@react-aria-nutrient/*"

[ritz078]

Closes

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

[iperzic]

Was this not possible to achieve using alias? Not only that seems like a more robust way to handle this, but it could save us potential conflicts whenever upstream import changes

[ritz078]

@iperzic How will you alias package name and publish it to npm ?

[darktasevski]

Just wondering, have we considered using company name as a scope for npm packages? For example @nutrient/react-aria.

[ritz078]

Just wondering, have we considered using company name as a scope for npm packages? For example @nutrient/react-aria.

@darktasevski It's not available 😢 https://www.npmjs.com/~nutrient otherwise we would have grabbed it for our main SDK itself.

[darktasevski]

Just wondering, have we considered using company name as a scope for npm packages? For example @nutrient/react-aria.

@darktasevski It's not available 😢 https://www.npmjs.com/~nutrient otherwise we would have grabbed it for our main SDK itself.

Well, that's disappointing :/

[iperzic]

How will you alias package name and publish it to npm ?

I referred to the fact that we still have to publish under a different name, but we don't have to change code occurrences of import, because it would be an alias that points original name, to our name.

[ritz078]

I referred to the fact that we still have to publish under a different name, but we don't have to change code occurrences of import, because it would be an alias that points original name, to our name.

The amount of custom code required to make imports work for storybook, jest and yarn might not be worth it. Brute force was just a faster approach. One thing we can do without changing much is keep the directory name same as earlier.

[iperzic]

Yeah, that would help somewhat.

TBH, I was mostly inspired for this by the other PR where my browser would completely freeze when reviewing 1993 files, so figured that it can be simplifies