fix single asterisk replacement in reverse-exports

[mansona]

I took the reverse-exports package out for its first real-world spin today by combining #1648 #1650 and #1653 into one giant mega branch 💪 ... but it didn't work 😂

I first looked at the error and thought "on no we need to update the blueprint because the exports are wrong" but thinking about it a bit better it looks like our reverse-exports could do with a little bit of love. This is totally expected in the dev process of the package since real-world examples will always beat lab-built ones 👍

@lolmaus if you could take a look at this and get the test passing that would be super 🎉

[lolmaus]

I have found this in the documentation:

* maps expose nested subpaths as it is a string replacement syntax only.

Also, the mention of ** the double asterisk glob in the documentation does not actually allow using it in keys or values!

The property of exports being statically enumerable is maintained with exports patterns since the individual exports for a package can be determined by treating the right hand side target pattern as a ** glob against the list of files within the package.

Thank you for the heads up, I know exactly how to fix it.

[lolmaus]

Fixed now!

[mansona]

I can't "request changes" since it's my PR 🙃 one minor thing and one that I would like to fix before we merge 👍

[mansona]

Looks good to me 👍

[lolmaus]

Great job, @lolmaus! 😂