This probably is hopefully just a symptom of my experience with node.js being near zero.
Iām attempting to use:
Iām running ParseServer locally and when I attempt to sign in using my Firebase credentials, I get to here in the file ./parse-server/lib/Adapters/Auth/index.js
As you can see, the module appears to have loaded but the keys āvalidateAuthDataā and āvalid
dateAppIdā of āoptionalAdapterā return null, even though they clearly exist in the prototype context of the watch window on the left.
As far as the server config is concerned, Iām launching with ānpm startā with a package.json file:
{
ānameā: āProjectNameā,
ādescriptionā: āparse-server for ProjectNameā,
āscriptsā: {
āstartā: āparse-server config.jsonā
},
ādependenciesā: {
āparse-serverā: ā^3.9.0ā,
āparse-server-firebase-authā: ā^1.0.0ā
}
}
The config.json file:
{
āappIdā: āxxxxxxxxxxxā,
āmasterKeyā: āxxxxxxxxxxxā,
āappNameā: āProjectNameā,
ācloudā: ā./cloud/mainā,
ādatabaseURIā: āmongodb://127.0.0.1:27017/parseā,
āauthā: {
āfirebaseā: {
āmoduleā: āparse-server-firebase-authā
}
}
}
Any suggestions as to why this might be happening would be gratefully received.
Just to add, Iāve had complete success with using the module that the one above is based upon but for a couple of reason I wonāt bore you with, Iād like to use the one thatās causing me problems.
This is the one that works:
Iām not sure whatās changed between the 2 thatās responsible for the issue but as I say, I have virtually no experience with ParseServer, node or javascript.