@uppy/core: fix TypeScript errors

[EricImpact]

@ts-expect-error directive is not needed; nothing wrong with defining tus as undefined.

Do some type narrowing of err in catch block to confirm it's an Error before returning message.

Closes #5592

[github-actions]

Diff output files

diff --git a/packages/@uppy/core/lib/Uppy.js b/packages/@uppy/core/lib/Uppy.js
index b4c89fe..05a12aa 100644
--- a/packages/@uppy/core/lib/Uppy.js
+++ b/packages/@uppy/core/lib/Uppy.js
@@ -520,7 +520,9 @@ export class Uppy {
     try {
       _classPrivateFieldLooseBase(this, _restricter)[_restricter].validateSingleFile(file);
     } catch (err) {
-      return err.message;
+      if (err instanceof Error) {
+        return err.message;
+      }
     }
     return null;
   }
@@ -529,7 +531,9 @@ export class Uppy {
     try {
       _classPrivateFieldLooseBase(this, _restricter)[_restricter].validateAggregateRestrictions(existingFiles, files);
     } catch (err) {
-      return err.message;
+      if (err instanceof Error) {
+        return err.message;
+      }
     }
     return null;
   }

[Murderlon]

Run corepack yarn build
Error: packages/@uppy/core/src/Uppy.ts(652,9): error TS2353: Object literal may only specify known properties, and 'tus' does not exist in type 'UppyFile<M, B>'.

Seems like it's needed afterall

[EricImpact]

Run corepack yarn build
Error: packages/@uppy/core/src/Uppy.ts(652,9): error TS2353: Object literal may only specify known properties, and 'tus' does not exist in type 'UppyFile<M, B>'.

Seems like it's needed afterall

I've updated the file to reinstate the @ts-expect-error flag, but placed it directly above the tus line. I couldn't test locally as I had issues trying to run npm install on the repo package, but hopefully this resolves the problem.

[Murderlon]

I wonder how much this PR will help because we use "useUnknownInCatchVariables": false everywhere, so there will be many, many instances where we don't do an instanceof check on the error. Only changing this doesn't seem to improve much.