-
Notifications
You must be signed in to change notification settings - Fork 13
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
provide done callback #23
Comments
we can! that totally makes sense, just wasn't using it that way at the time I made this. I guess the question is, when you call the node api now it writes the manifest for you. are you wanting it to keep doing that, or if you use the callback then don't write it to the filesystem and leave it up to whoever is using it that way? |
i'll totally add the babel plugin for the exports stuff so we don't have to do .default as well, ugh forgot about that. |
i'm thinking if a person is using the node api, then they should use the manifest however they want and it won't write the file? |
@kellyrmilligan apologies for late reply. I agree, if you provide a callback it makes sense to prevent file write and let the consumer do what they want. That way they can decide what to do with the file (write, inject into next build step, keep in memory, write async, etc.) |
@kellyrmilligan if you don't mind I'd like to take a stab at a PR for this?! |
@kellyrmilligan +1 for babel, .default. FYI, in my example, i stole it from a build process where I don't have the luxury of transpile |
Go for it! |
can we add a node style done callback?
I was thinking of something like this:
then we can promisify it
The text was updated successfully, but these errors were encountered: