Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
calendar Quickstart.js should write token using fs.writeFileSync, not fs.writeFile.
See original GitHub issuefs.writeFile does not wait for the writing to complete, and I would end up with an empty /.credentials/calednar-nodejs-quickstart.json file. This of course would crash the app on subsequent starts as it either expects the file to NOT EXIST, or it to exist and have some data.
My fix was to replace fs.writeFile(TOKEN_PATH, JSON.stringify(token)); with fs.writeFileSync(TOKEN_PATH, JSON.stringify(token), 'utf8');, thus insuring that the program actually writes the file.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ah! So yes, the tutorial is out of date. However, the readFile part looks right. We’re in the process of updating and testing out samples, so apologies for the confusion!
The tutorial at https://developers.google.com/google-apps/calendar/quickstart/nodejs still seems to reference fs.writeFile instead of fs.writeFileSync. Was it updated somewhere else?
And if not changed already, the
const google = require('googleapis');should beconst {google} = require('googleapis');(same as #999 )