feat(content-loader): set baseUrl to location.pathname when initialized

[leo6104]

With this commit, we don't need to pass [baseUrl] everytime for Safari browser.

It will set baseUrl to window.location.pathname if it can access to window object.

[leo6104]

I read the issue (danilowoz/react-content-loader#93) and PR (#38) and understand all situations.

I know that it is not same way to support baseUrl parameter in react-content-loader implementation.
However, In Angular, <base href="/"> tag is default option in index.html so i think it would be better to always set to location.pathname. Please consider it :)

[NetanelBasal]

And it will also work without the baseUrl?

[leo6104]

@NetanelBasal Yes. I apply this commit on our company services and it works without baseUrl.

3 condition i considered.

1. If user set [baseUrl] input, it will not overwrite to location.pathname and use the input.
2. If user not set [baseUrl], it will set baseUrl variable to location.pathname automatically.
3. If it is server-side rendering, not set to window.location.pathname. (because window object is not defined in Node environment)

[NetanelBasal]

Resolve the conflicts, please.

[leo6104]

Resolved! :)