fix: fuselage-hooks bundling #258
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
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 aims to fix two bundling-related issues of
@rocket.chat/fuselage-hooks:@rocket.chat/fuselage-tokensisn't bundled correctly as it's treated as an external dependency;microbundleis outdated (e.g. no support for optional chaining).To accomplish that, we reverted to
rollupas the bundler and setES5as the target intsconfig.json, while addingcommonjs,esmandumdbuild formats.Additionally, the README file was updated and clean, and the API Extractor is being tested as an alternative to generate API reference documentation.