feat: set fetch options #75
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Certain packages export different contents depending on the target platform for compilation. For example, there is a significant difference bundling @solid-js/web for the server versus the client, eg. https://esm.sh/stable/[email protected]/deno/web.js & https://esm.sh/stable/[email protected]/es2022/web.js.
By allowing users to set the
user-agentheader we can bundle for different targets besides deno. I'm think there could also be other usecases for this, such as bundling authenticated resources etc.I've gone ahead and passed an RequestInit object from the plugin options to the portable loader. It doesn't seem like it's possible to change how the native loader fetches data though.