Skip to content

More examples on how to load rdkit-js in various javascript and typescript context #159

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MichelML opened this issue Aug 7, 2022 · 6 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@MichelML
Copy link
Collaborator

MichelML commented Aug 7, 2022

See context of this issue here #150 (comment)

@heberleh more thoughts welcome here 👍

@MichelML MichelML added documentation Improvements or additions to documentation enhancement New feature or request labels Aug 7, 2022
@MichelML MichelML changed the title More detailed example on how to load rdkit-js in various javascript and typescript context More examples on how to load rdkit-js in various javascript and typescript context Aug 7, 2022
@MichelML
Copy link
Collaborator Author

MichelML commented Aug 9, 2022

#124

@MichelML
Copy link
Collaborator Author

Aligned with this idea, starter templates for projects in various stacks could be great.

@twoXes
Copy link

twoXes commented Dec 4, 2022

Interested in a Sveltekit example? Am currently working on it...that is of course if I ever figure out how to install :0

@MichelML
Copy link
Collaborator Author

@Ramb0a yes of course, and sorry for the delays! I created an issue for you #290

Have you been able to load rdkit-js in your project?

@duerrsimon
Copy link

@twoXes Did you ever get it to work in Svelte?

@occamsystems
Copy link

Having just now gotten this working with Angular, I can say that by far the biggest (apparently) missing piece of documentation was the need to add the wasm blob and RDKit_minimal.js to the angular.json configuration in order for initRDKitModule() to be loaded.

It took me a couple hours to figure this out, and there is a decent chance that many developers would takes days to get there if they did it at all, since this is not the type of operation that is required for "native" Angular libraries.

I think this information could very easily be added near the top of the page on https://angular.rdkitjs.com/ to prevent such issues.

It may be that other frameworks have a similar missing configuration step that is tripping them up, since, apart from this, everything felt very straightforward using npm install.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants