Error while upgrading from 7.3.0 to 8.0.0

[ihardyslide]

Error while upgrading from 7.3.0 to 8.0.0

[ihardyslide]

Nevermind, I solved it somehow by multiple times cleaining npm cache and deleting package-lock.json and node_modules and installing again.

[ihardyslide]

Sorry for reopening, but now I experience a different error.
Suddenly, the typecheck which runs with the build is also type checking d.ts files inside node_modules folder.
This breaks the build because of ~500 errors.

example:
node_modules/graphql-redis-subscriptions/node_modules/ioredis/built/utils/RedisCommander.d.ts(3574,122): error TS1005: ',' expected.

Do you have any idea what is causing this? I am on coral version 8.0.4 now.

[losowsky]

Got it - can you confirm you've been following the steps in our migration docs? https://docs.coralproject.net/migrating-7-to-8

[ihardyslide]

Hi,

I've read the migration docs, but the only thing which is actually to do according to this, is to adapt the available ressources for redis and mongo.
Since I can not even get the build to work, I can not start Coral and therefore the connections to the databases are not even established yet.
So I do not know what could interfere here with the build.
Did I miss something?

Thanks for quick response.
BR

[ihardyslide]

I meanwhile tried to add --showConfig to the tscheck npm scripts, like so:

"tscheck:client": "tsc --showConfig --project ./src/core/client/tsconfig.json --noEmit",
"tscheck:scripts": "tsc --showConfig --project ./tsconfig.json --noEmit",
"tscheck:server": "tsc --showConfig --project ./src/tsconfig.json --noEmit",

This showed me, that the config is actually correct (skipLibCheck:true and exclude: ["node_modules"]), and also at the mentioned files, there is nothing to be seen from node_modules.

Output from above:
https://pastebin.com/dqRfAPWp

But as soon as I run the tscheck normally without this parameter, following errors are produced:
https://pastebin.com/9r1sHvTA

And these are the files I get output when I add the --listFiles parameter (--explainFiles ist not available yet in this typescript version):
https://pastebin.com/mgCFFk2V

[kabeaty]

Hello, I’ve looked into your links and errors that you’re seeing, and it’s a tough one to troubleshoot from afar. It definitely seems like something has somehow gotten incorrectly installed. It sounds like you’ve already removed node_modules and done a clean install of your npm cache with npm ci, which is what I would do and recommend in this case. I would probably also double-check my node and npm versions. Do you have any more updates or info to share that might help figure it out?

[ihardyslide]

Hi, I was able to get rid of the errors by rolling back to a commit where I did not yet delete package-lock.json and node_modules.
Then I manually editet the package-lock.json and replaced the sha512 hash to get rid of the EINTEGRITY error I mentioned initially in this issue.
After this, I could install normally and continue with the upgrade.

Meanwhile I was able to upgrade to the latest version.

Unfortunately I have no idea why this errors happened.

Anyway I guess this can be closed, thanks.

[kabeaty]

Happy to hear that you got this figured out! I'll close this issue then.