-
Notifications
You must be signed in to change notification settings - Fork 61
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
Implement filesystem ops #17
Comments
Do you have a full list of all APIs that need to be implemented to achieve parity? HTTP client, HTTP server, FS, these are all good examples, which I suppose will all wrap the Go stdlib? Anyway, perhaps the list is just the Node stdlib but I'm curious what your thoughts are. |
I think we'll want to implement all the most commonly used APIs first and then think about if we'd want to expand more (this will be a seperate discussion as to how minimal we want to be)
for ref: https://doc.deno.land/builtin/stable |
Sure, maybe add some utility methods to read directly utf-8 files since they are the most common |
We're using Afero in #25 |
All of the above listed APIs have been added 👍 |
The goal right now is to implement all the file system APIs provided by Deno - https://github.com/denoland/deno/blob/master/cli/ops/fs.rs
There is already a
Elsa.readFile
binding incore/dispatch.go
with it's corresponding js call atjs/01_namespace.js
.Looking forward to recieve PRs 😄
The text was updated successfully, but these errors were encountered: