Make this package browser friendly

Hello we have a use case that we want to use this plugin in the browser and bundle it via webpack.
Currently the FileSystemLoader is being use as a fallback loader if no load provided via the config, and it is always imported by the package index.

The issue is:
FileSystemLoader imports nodejs fs module and that's not browser friendly (needs config in order to bundle).

I have few suggestions for solutions to this issue:

1. Add "browser" field to the package.json that will implement a "loader" that throws something like "when using this package in browser you must provide a custom loader"
2. Create entrypoint specifically for browser usage which does not import FileSystemLoader by default
3. Allow inject the fs module to the loaders avoiding importing it directly (split the index into a factory that will accept fs)

These are non-breaking changes that can be done here.

We are willing to make this PR.

Please advice.

Start by reading the package index and FileSystemLoader, then inspect package.json and reproduce the webpack bundle issue caused by importing Node.js fs. Compare the proposed browser field, browser entry point, and injected fs approaches; done means browser consumers can bundle the package with a custom loader without requiring fs configuration.