Skip to content
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

unlink always throws an error #34

Open
neil-lindquist opened this issue Sep 1, 2020 · 0 comments
Open

unlink always throws an error #34

neil-lindquist opened this issue Sep 1, 2020 · 0 comments

Comments

@neil-lindquist
Copy link

I'm getting errors when my code calls unlink.

...\temporary\lib\file.js:100 Uncaught Error: null
    at ...\temporary\lib\file.js:100
    at FSReqCallback.oncomplete (fs.js:150)

Looking at the node.js filesystem docs, the callback's argument needs to be checked whether it's an error. However, the code for this library always throws the object.
My code works without the error if I pass a callback of (in Coffeescript) (err) -> if err then throw err, so I'd recommend changing to something similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant