You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to use the MCSS functions which were recently made available in MinimalLib, but the RDKitModule object generated from the latest npm package (2024.3.5.1) does not expose them.
Describe the solution you'd like
I understand that there are drawbacks in exposing every method that's available to the standard package that is distributed to millions of users, because it can increase substantially the payload.
I would like to have access to a version of RDKit.js that contains the latest features. This could be distributed along with the current version. One would have to either copy the correct file from the node_modules dir or point to the correct module in the import directive.
Describe alternatives you've considered
Other alternatives could be to compile my own version of RDKit. The issue is that the artifacts must be available to other third parties (e.g. in CI pipelines or other users)
Additional context
None
(as an aside, I've noticed that the npm package contains 2 copies of the 6.3MB wasm file, one in /dist and one in /Code/MinimalLib/dist)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I would like to use the MCSS functions which were recently made available in MinimalLib, but the RDKitModule object generated from the latest npm package (2024.3.5.1) does not expose them.
Describe the solution you'd like
I understand that there are drawbacks in exposing every method that's available to the standard package that is distributed to millions of users, because it can increase substantially the payload.
I would like to have access to a version of RDKit.js that contains the latest features. This could be distributed along with the current version. One would have to either copy the correct file from the node_modules dir or point to the correct module in the import directive.
Describe alternatives you've considered
Other alternatives could be to compile my own version of RDKit. The issue is that the artifacts must be available to other third parties (e.g. in CI pipelines or other users)
Additional context
None
(as an aside, I've noticed that the npm package contains 2 copies of the 6.3MB wasm file, one in /dist and one in /Code/MinimalLib/dist)
The text was updated successfully, but these errors were encountered: