Conversation
| */ | ||
|
|
||
| import { Module } from "../js/module.js"; | ||
| import { Module } from "./module.js"; |
There was a problem hiding this comment.
This will mess up the PyProxy API docs.
There was a problem hiding this comment.
I guess we can make a symlink pyproxy.js ==> ../core/pyproxy.gen.js.
There was a problem hiding this comment.
Actually the output it doesn't seem to be messed up so I guess this change is fine by itself.
| Download and extract Pyodide packages from [Github | ||
| releases](https://github.com/pyodide/pyodide/releases) | ||
| (`pyodide-build-*.tar.bz2`). The version of the release needs to match exactly the version of this package. |
There was a problem hiding this comment.
We should try to simplify this by copying the build directory into src/js in the prepublish script.
There was a problem hiding this comment.
I agree that we need to simplify it, but as discussed in #14 (comment) I'm not convinced that bundling all packages is the solution. We need a solution that would also work for micropip installed packages anyway.
So I'm planning to add some local caching next and support remote CDN in node so there is no difference between browser and node usage when starting Pyodide.
|
Merging. We can improve this in follow up PRs. |
2 participants
Changes to be able to release of src/js as a standalone NPM package (https://www.npmjs.com/package/pyodide).
Closes #328
xref: #14
Will add more documentation for using Pyodide in Node (#1725) in a follow up PR.