docs: update readme and types to reflect alternate wasm loading path - #362
Merged
Conversation
|
Someone is attempting to deploy a commit to the invivoai-platform Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
|
LGTM @sgoodrow-zymergen , thanks for this! |
MichelML
added a commit
that referenced
this pull request
Aug 24, 2023
docs: update readme and types to reflect alternate wasm loading path
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.
For some servers, the loading script will not be in the same location as the WASM module file.
Update documentation and types to reflect how to load rdkit-js from an alternate path.
Additional context from this discussion: #360 (reply in thread)