-
Notifications
You must be signed in to change notification settings - Fork 110
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
fs.writeFile throws ERR_INVALID_CALLBACK #566
Comments
@koebeen I've been running into this, too. I had to ensure that I was running on Node 8 (which is the LTS right now). I hope this helps! |
Yep, using Node 8 resolved the same error for me as well. |
thanks guys. yeah, obvious in the end. i should have run the lts.. |
Yes, please close it
…On Thu, Nov 29, 2018 at 8:41 AM Felipe Buenaño ***@***.***> wrote:
@koebeen <https://github.com/koebeen> @awayken
<https://github.com/awayken>
Is this issue resolved? Could it be closed?
Thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#566 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AlOHozbJRAQFestCzbKJ9s9kX2YTlQ2Jks5uz_IOgaJpZM4VZo3U>
.
|
Is Node v8 required to use kyt? I'm getting invalid callback error when following getting started instructions verbatim. If this is the case, it seems that either updating kyt to work with Node 10 or mentioning in the ReadMe that Node 8 is required would be appropriate, as Node 10.x is listed as the current LTS version. |
Node v10 is now LTS, when can we expect a solution for this? |
What worked for me, was editing webpack-version-file-plugin > index
Note after the flag options, I just added a blank callback function. Then the build continued unhindered. Hope this helps someone. |
Versions of kyt, node, OS
kyt 0.9.0
node 10.6.0
OS macos 10.11.6
Bug or Feature?
Bug
Current Behavior
yarn dev or npm run dev results in an error
Desired Behavior
no error is thrown. app runs.
Fix:
line 72 of webpack.base.js shoud read:
fs.writeFileSync(assetsFilePath, JSON.stringify(assets, null, ' '), 'utf8');
instead of:
fs.writeFile(assetsFilePath, JSON.stringify(assets, null, ' '), 'utf8');
Full error:
The text was updated successfully, but these errors were encountered: