-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
Failed to import - micromark #179
Comments
still having this error on v55:
|
now there is this error:
|
@ije could you clean up the build dir for CDN then please |
Still having a problem in importing > import { micromark } from 'https://esm.sh/micromark@3.0.10'
Uncaught SyntaxError: The requested module '/v64/micromark@3.0.10/deno/lib/postprocess.js' does not provide an export named 'postprocess'
at async <anonymous>:2:29 // https://esm.sh/micromark@3.0.10/deno/lib/postprocess.js
/* esm.sh - error */
throw new Error("[esm.sh] " + "parseCJSModuleExports: Package path ./deno/lib/postprocess is not exported from package /tmp/esm-build-1af3155c4d51507d2cc6db59e44781bab679561a-505e9804/node_modules/micromark (see exports field in /tmp/esm-build-1af3155c4d51507d2cc6db59e44781bab679561a-505e9804/node_modules/micromark/package.json)");
export default null; You can see a function |
Similar on v65: $ deno eval 'import { micromark } from "https://esm.sh/micromark"' Yields:
For some reason |
Awesome! |
Nice work! |
Thanks for v66, I finally succeed in importing MDX in deno! import "https://esm.sh/@mdx-js/mdx@v2.0.0?pin=v66&alias=astring:https://deno.land/x/astring@v1.8.1/src/astring.js";
Module {
compile: [Function: T],
compileSync: [Function: _],
createProcessor: [Function: j],
evaluate: [AsyncFunction: $e],
evaluateSync: [Function: Ke],
nodeTypes: [
"mdxFlowExpression",
"mdxJsxFlowElement",
"mdxJsxTextElement",
"mdxTextExpression",
"mdxjsEsm"
],
run: [AsyncFunction: L],
runSync: [Function: N]
} |
@aiotter cool! |
Failing module
Error message
After running
deno run
I get this:Additional info
Related: #135
The text was updated successfully, but these errors were encountered: