chore: upgrade to babel-plugin-macros

[Haroenv]

I didn't do extensive testing, but the tests pass and @kentcdodds said there were no breaking changes…

fixes #515

What: changed babel-macros to babel-plugin-macros

Why: this is the new name and the one that is going to be incorporated in CRA

How: pretty much find and replace babel-macros for babel-plugin-macros

Checklist:

• Documentation
• Tests
• Code complete

[Haroenv]

The tests completely fail on my end because eslint (prettier) expects trailing commas, while they seem to be explicitly forbidden over the code base

[tkh44]

Thanks @Haroenv I'll look at that right now.

[Haroenv]

tests are failing on CI because of unrelated linting, AFAICT #526 should fix that

[Haroenv]

voilà, now without the accidental trailing commas @tkh44 🤷‍♂️

[tkh44]

Thanks again

[Haroenv]

With pleasure, glad @kentcdodds made it such a smooth upgrade path

[tkh44]

Is there anything else you would like to release with this @mitchellhamilton? Should we backport this to 8? or just run with putting it in 9?

[Haroenv]

I just saw the commit message said emotion, but that should have been macros

[emmatown]

@tkh44 Let's just put it in 9 since AFAIK macros built with babel-macros are compatible with babel-plugin-macros.

Maybe @kentcdodds can correct me if I'm wrong?

We could do a release now with this and #516 to next.

[kentcdodds]

Yes, it should actually be totally compatible. All macros using babel-macros to be created should work with the babel-plugin-macros transform because the creation just sets a few properties on your function so it should work :)