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
The library published on npm works only on the client-side. Support for the pigmnts library on server-side using Node.js can be implemented considering following points:
pigments_node() function can be implemented that is compatible with Node.js and does not depend on Browser APIs like canvas.
The existing pigments() function may depend on pigmnts_node() function making it easier to interact with the library on the client-side by abstracting canvas APIs.
The library published on npm works only on the client-side. Support for the pigmnts library on server-side using Node.js can be implemented considering following points:
pigments_node()
function can be implemented that is compatible with Node.js and does not depend on Browser APIs like canvas.pigments()
function may depend onpigmnts_node()
function making it easier to interact with the library on the client-side by abstracting canvas APIs.wasm-pack
supports multiple outputs targets, but combining them under a single package is a little messy. Hoping for this to be merged [WIP] Introduce anAll
target for outputting all supported module types by wasm-pack rustwasm/wasm-pack#705The text was updated successfully, but these errors were encountered: