breaking: remove polyfills & top level await #41
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
some ppl have had issues with top level await and my way of loading stream polyfills from a CDN
This will totally remove all top level await and dependency on
fetch-blob
and web stream polyfills and making it zero dependent on any other library. considering now that all green env now has WritableStream, ReadableStream, TransformStream, Blob, File, and DOMException globally now.right now if you want to use it in NodeJS and want to get a File class from
handle.getFile()
then you would have to install the optional dependency offetch-blob
in order to use thefileFrom(path)
alsoHowever if you depend on some older environment then there is an option to do so using the config
closes #36
closes #20