Peter Murphy

Thank you for getting back to me. My point is that I don't (well, *didn't*) need everything. Documenting an API should not take 200 pages. *Perhaps* it could take 20...

Of course he doesn't owe us anything, @Akazm. But I'm trying to hint pretty strongly that he actually has some control over whether Module Federation is *used* or *not*, one...

@ScriptedAlchemy: I am very pleased that you are opening a PR. I would also be willing to help with guidance and wording. One bit of advice I'd add is maybe...

@patrickCode That would be very much appreciated. Thank you/

You are going to have to accept anchor and aliases. The anchor "&id001" at "labels" is saying "Here's some data which we will want to refer to later", and the...

Your link doesn't change the situation that your YAML has the same piece of data referred to *three* times, and thus needs anchors and aliases to refer to them. Can...

That may work for you. What does the resulting YAML look like? Hopefully, you haven't lost data in the process. If you have *copies* of the original data at the...

I got the same problem on expo. The current version of sync-storage relies on '@react-native-community/async-storage', but '@react-native-community/async-storage' is not supported there!

I got the same issue. I think the problem here is that the owner of the `build` directory created by the process appears to be `root`. (Yes, I am the...