fix: check for url being null before accessing __esModules property

[charlessuh]

This PR contains a:

• bugfix
• new feature
• code refactor
• test update
• typo fix
• metadata update

Motivation / Use-Case

Perhaps this is an unusual use case, but I'm using a custom final loader which can export null (i.e. the source is module.exports = null), e.g. if it determines a module will not be needed.

I suppose I could export an empty object, but in some cases I need to check if a module was removed in this manner, and it's easier to check for null which is falsy (as opposed to an empty object which is truthy.)

Breaking Changes

n/a

Additional Info

n/a

[jsf-clabot]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

[codecov]

Codecov Report

Merging #1005 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #1005   +/-   ##
=======================================
  Coverage   99.54%   99.54%           
=======================================
  Files          10       10           
  Lines         435      435           
  Branches      127      127           
=======================================
  Hits          433      433           
  Misses          2        2

Impacted Files	Coverage Δ
src/runtime/getUrl.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80e9662...5d02a87. Read the comment docs.

[alexander-akait]

Need test

[alexander-akait]

What is use case using null? Can you provide example?