Add esbuild overwrites #580
Merged
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
FedeIlLeone
added
enhancement
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.
This PR adds the ability for plugin & theme developers to overwrite the replugged esbuild config.
This is especially useful for when plugin developers need special configurations for their plugin to build - eg. adding font loaders for their css files.
The reason its a function rather than just extra config values is to allow developers to write their own plugins without removing the current required plugins.
The reason I chose to name the extra config file
esbuild.extra.mjsis to avoid editors like vscode from using interpreting aesbuild.(m)jsfile as the thing to use for building (it causes a lang server crash)This only affects plugin developers - this does not need a new replugged version release, just a new npm package.