fix: resolve opts when no-config & fix vulns

[evenstensberg]

What kind of change does this PR introduce?
Closes #1023
Did you add tests for your changes?
Yes
If relevant, did you update the documentation?
N/A
Summary
Dupes out of resolving options if there are none to throw an error

Does this PR introduce a breaking change?
No
Other information
N/A

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

[ematipico]

Now that you have the if/else, options will never be undefined right? So this additional check is not needed

[evenstensberg]

checks for options.then object prop so will throw. We're setting props on the object later these checks, I think we "assumed" we either found or did not find the props before validating args that aren't protected by 0CJS (entry and output)

[ematipico]

I'm not talking about .then, I'm talking about options &&. It's redundant. You already assigned it before with options = {}.

So or you keep this check and remove the assignment or keep the assignment and remove the check.

[evenstensberg]

Thanks for pointing it out, changed now!

[webpack-bot]

@evenstensberg Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@ematipico Please review the new changes.

[ematipico]

Please review assignment/check of options

[ryanspice]

pulled, tested, and compiles for me now after experiencing #1023