-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
fix: cjs export rewritten to invalid identifier #21853
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
thanks for such a quick fix. However it didn't work for me. Per instructions for MacOS m1/m2, I built the subsequent canary, with the fix in ext/node/analyze.rs . Unfortunately looks like "deno --version" stopped giving the canary hash recently, so that useful info is no longer available by command line. I don't know how else to determine it? But here's a snippet from the source to verify that analyze.rs has the current fix:
And here is the same import failure result. It works for pl, still fails for Plotly.
|
@gplanansky so it works if you build from source but not if you |
If I am doing it right, deno still fails importing plotly:
|
@gplanansky I see what you mean. The error you are getting is now completely different so it's a completely different bug now. Could you open a new issue about it? |
@bartiomieju deno import Plotly error: Cannot read properties of undefined (reading 'navigator') #21871 |
<!-- Before submitting a PR, please read https://deno.com/manual/contributing 1. Give the PR a descriptive title. Examples of good title: - fix(std/http): Fix race condition in server - docs(console): Update docstrings - feat(doc): Handle nested reexports Examples of bad title: - fix #7123 - update docs - fix bugs 2. Ensure there is a related issue and it is referenced in the PR text. 3. Ensure there are tests that cover the changes. 4. Ensure `cargo test` passes. 5. Ensure `./tools/format.js` passes without changing files. 6. Ensure `./tools/lint.js` passes. 7. Open as a draft PR if your work is still in progress. The CI won't run all steps, but you can add '[ci]' to a commit message to force it to. 8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label. --> Fixes #21836
Fixes #21836