Chemdoodle-next NPM

ChemDoodle for Next.js

Due to Next.js's runtime is not fully client runtime(even though you declared 'use client'). The parameter(like module.exprots) of node runtime will be added through Next.js's pack, and the ChemDoodle uses UMD for module build, which means it judge code runtime by parameters like exports, module.exports, which will make a wrong judge result and cause error in web

I have fixed this issue temporarily by deleting the UMD judge code in ChemDoodle(which means it only works fine at web)

Useage

see code in example

Chemdoodle Next.js

acorn acorn-import-assertions ajv ajv-keywords browserslist buffer-from caniuse-lite chrome-trace-event clone-deep colorette commander cross-spawn electron-to-chromium enhanced-resolve envinfo es-module-lexer escalade eslint-scope esrecurse estraverse events fast-deep-equal fast-json-stable-stringify fastest-levenshtein find-up flat function-bind glob-to-regexp graceful-fs has-flag hasown import-local interpret is-core-module is-plain-object isexe isobject jest-worker json-parse-even-better-errors json-schema-traverse kind-of loader-runner locate-path merge-stream mime-db mime-types neo-async node-releases p-limit p-locate p-try path-exists path-key path-parse picocolors pkg-dir punycode randombytes rechoir resolve resolve-cwd resolve-from safe-buffer schema-utils serialize-javascript shallow-clone shebang-command shebang-regex source-map source-map-support supports-color supports-preserve-symlinks-flag tapable terser terser-webpack-plugin undici-types update-browserslist-db uri-js watchpack webpack-merge webpack-sources which wildcard

1.0.1

3 months ago

1.0.0

3 months ago