[Solved] "SyntaxError: Unexpected token M" when running meteor

help
1

Today, while trying to run my project on dev server, i got this error and i don’t know what cause it. I’ve not installed anything new or updated anything (trying to avoid something like this) but it happened anyway.

i’ve tried to find the “auth.js” or “stat.js” file, mentioned below but couldn’t find them (maybe im searching in the wrong place)

well, below is the trace. hope you can help me.

=> Started proxy.
/home/wa-p/.meteor/packages/meteor-tool/.1.6.1_1.b2gglq.hyzdq++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:218
throw error;
^

SyntaxError: Unexpected token M in JSON at position 94
at JSON.parse ()
at readSessionData (/tools/meteor-services/auth.js:145:15)
at Object.exports.getSessionId (/tools/meteor-services/auth.js:872:32)
at /tools/meteor-services/stats.js:64:23

EDIT:

here is another part of the error trace when running “meteor --verbose”

=> Started proxy.
Error inside updater.
SyntaxError: Unexpected token M in JSON at position 94
at JSON.parse ()
at readSessionData (/tools/meteor-services/auth.js:145:15)
at Object.tryRevokeOldTokens (/tools/meteor-services/auth.js:299:10)
at checkForUpdate (/tools/packaging/updater.js:41:8)
at Object.exports.tryToDownloadUpdate (/tools/packaging/updater.js:32:3)
at Updater._check (/tools/runners/run-updater.js:39:15)
at Promise.asyncApply (/tools/runners/run-updater.js:25:12)
at
/home/wa-p/.meteor/packages/meteor-tool/.1.6.1_1.b2gglq.hyzdq++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/meteor-promise/fiber_pool.js:43:40

2

Hi Wa-p,
did you meteor npm install meteor-node-stubs ?
and can you show us your package.json file ?

3

After reading a lot of forums and trying a lot of option, finally found one that did the trick.

It seems like a file has gone corrupted. In a forum, someone with a similar log trace said he fixed it by doing: " sudo rm ~/.meteorsession " … i tried and it worked.

i don’t know why this happened or why this was the solution, but i’m considering this case closed.

thx @guidouil.

2 Likes