Make package name required for "link"

[grabbou]

When you don't pass a package name to the "react-native link", it will try to look for all packages to link from your node_modules.

This is causing us a lot of issues, such as linking wrong packages or the ones that someone doesn't want to link (e.g. decided to use a different way of linking that is out of scope for this command).

We should simply stick to requiring package name.

[grabbou]

Please leave a comment if you are using react-native link to link your project assets and describe your use case. This behaviour will be also deprecated since the name of the package is going to be required.

[ltcaosj]

I would like to be able to link my assets to iOS and Android projects.
I can do it with RN 0.57.8, but I cannot with RN 0.59.x

[Esemesek]

Yup. We plan to introduce a new command or flag that will link only project assets. For now, you should be able to link project assets with react-native link, but it is deprecated.

[ltcaosj]

thanks @Esemesek

[sijad]

currently it's not possible to link root assets with RN 59 rc2.

I've changed () => linkAssets(platforms, project, assets) to () => linkAssets(platforms, project, { assets }), in linkAll
and it worked, but I'm not sure if it's proper fix.

[Esemesek]

@sijad This is a bug. linkAll should link root assets. I'll fix that in a minute.

[kennetpostigo]

I use it to link my font assets