node-tutorial | Source code for All about NodeJS Series | Runtime Evironment library

Regarding the module.filename problem - you can read this discussion or just that comment: https://github.com/webpack/webpack/issues/1599#issuecomment-328540024

quote:

aprilmintacpineda commented

for those having this issue, it is also good to note that module.filename would be undefined if you bundled your files. In my case it was undefined and I fixed it by simply replacing it with __filename which yields the same outcome.

So you should be able to replace path.basename(module.filename); with path.basename(__filename);.

But it still would be a bundled js file in /dist folder and your models are in /postgres/models folder, as I understand.

1) To not to automatically load your models, but directly require all necessary models.

assuming this file's path is /postgres/models/index.js and actual models are in the same folder not tested

Just a suggestion: have you tried resolving the problematic path before passing it to webpack? Something along the lines: path.resolve(__dirname, './src/client') will convert the path from relative to absolute and often times it helps to quiet various loaders.

try consoling req.files.filename.

I found filename in req.files.filename.

Correction - req.files is array of object.

Try this, change app=express; to app=express();

When you await an function like you do with getAddressFromDB, that function needs to return a promise. In your code, you are returning undefined because your return statement is always executed before the callback of the database operation is done executing. Adding async does not change that.

You can fix this by defining a promise and returning it, like this (see comments in the code for further explanation):

This sounds like you need to update your scope list to include a missing scope. I don't know what the scope is that you need, but what I would do is in Graph Explorer, after you are logged in, I'd open the console and run tokenPlease() to get your access token. Compare the scopes in the access token returned by Graph Explorer to the scopes that you request in your app to help you determine which scope you still need to request.

First you should update those dependencies to:

Apparently there are two versions of calendar sharing, which I'll refer to as the "old" and the "new". The details aren't important, it's sufficient to know that this is an implementation detail within Microsoft's clients (Outlook, OWA, etc.). In your case, the person that shared their calendar with you did so with a client that used the "old" method, and the REST API doesn't have access to calendars shared with that method. We're working on addressing that problem in the API.

In the meantime, if the user that shared their calendar can remove the sharing, then use Outlook on the web, Outlook on iOS, or Outlook on Android to re-share, it should unblock you. (With the requirement that their mailbox is hosted on Office 365).