Add new packagerOptions: noNonInteractive to disable interactive mode when using Yarn 2 or above

[jagonzalr]

What did you implement:

Closes #642

How did you implement it:

Add a new flag noNonInteractive to packagerOptions when using yarn as the packager.

If using Yarn 2 or above the flag --non-interactive will break yarn install.

How can we verify it:

npm run test

Todos:

• Write tests
• Write documentation
• Fix linting errors
• Make sure code coverage hasn't dropped
• Provide verification config / commands / resources
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES
Is it a breaking change?: NO

[j0k3r]

Looks ok to me.
I'm wondering if this kind of option could be "transparent" without too much overload, like we check Yarn version and if the version < 2, we apply the --non-interactive option.

[jagonzalr]

Looks ok to me. I'm wondering if this kind of option could be "transparent" without too much overload, like we check Yarn version and if the version < 2, we apply the --non-interactive option.

Interesting idea, let me have a look at that

[vicary]

LGTM in its current state, I also quite like the transparent idea.

Sidenote:

1. If version detection for yarn is possible, --frozen-lockfile option should be translated to --immutable.
2. If even more arguments are found diverging between v1 and v2, we may have to split it out to a new file e.g. lib/packagers/yarn-berry.js

[jagonzalr]

@j0k3r @vicary if this is good I would prefer if it can be merged and published.

This fixes the current issue of not being able to used Yarn 2 or 3 which forces people to go to Yarn 1.

I can work on a different PR where it can implement the more transparent solution later.

[j0k3r]

@jagonzalr Yep, we'll merge it and if you want to work on an improved version, we'll be happy to review it 👍🏼

[Jameskmonger]

Is there a known timeline for this update to be published to npm? Thanks ❤️

[j0k3r]

In the coming days I guess