🐛 Skip non-documentable .wasm exports in doc generation#1157
Merged
Conversation
The @effectionx/inline package exports a ./swc entry pointing to a WASM binary build artifact. This file doesn't exist in git clones and isn't parseable as TypeScript, causing the website build to crash with a readTextFile ENOENT error.
commit: |
taras
approved these changes
Apr 21, 2026
This file contains hidden or 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
2 participants
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.
Motivation
The website build crashes when generating docs for
@effectionx/inlinebecause itspackage.jsonexports include a./swcentry pointing to a WASM binary (swc/target/wasm32-wasip1/release/swc_plugin_inline.wasm). This file is a Rust build artifact that:.gitignore)The doc loader's
Deno.readTextFile()call hits an ENOENT, breaking the entire site build.Approach
Add an
isDocumentable()filter innormalizeExports()that skips.wasmfile exports before they reach the doc generation pipeline.Possible Drawbacks or Risks
If a future package legitimately needs documentation generated from a
.wasmexport, it would be silently skipped. This seems unlikely since WASM binaries aren't source-documentable.