OMG!!!!

For the last couple of days I was seeing a TypeScript linting related error after upgrading to

eslint

v8,

@typescript-eslint/eslint-plugin

and

@typescript-eslint/parser

v5.1 and so had turned off linting in sst. The error still persists here unfortunately, it seems the linter versions 4 and 5 have incompatibilities. This could be a tricky one for you guys to manage going forward unless you can maybe find a way for the user to 'bring their own version' Error, for reference is:

Error: Rules with suggestions must set the `meta.hasSuggestions` property to `true`. `meta.docs.suggestion` is ignored by ESLint.
Occurred while linting /Users/rosscoundon/Documents/GitHub/omw-pso-be/src/main/utils/Log.ts:64
Rule: "@typescript-eslint/no-explicit-any"
    at Object.report (/Users/rosscoundon/Documents/GitHub/omw-pso-be/node_modules/eslint/lib/linter/linter.js:946:39)
    at TSAnyKeyword (/Users/rosscoundon/Documents/GitHub/omw-pso-be/node_modules/@serverless-stack/cli/node_modules/@typescript-eslint/eslint-plugin/dist/rules/no-explicit-any.js:183:25)
    at ruleErrorHandler (/Users/rosscoundon/Documents/GitHub/omw-pso-be/node_modules/eslint/lib/linter/linter.js:966:28)
    at /Users/rosscoundon/Documents/GitHub/omw-pso-be/node_modules/eslint/lib/linter/safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (/Users/rosscoundon/Documents/GitHub/omw-pso-be/node_modules/eslint/lib/linter/safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (/Users/rosscoundon/Documents/GitHub/omw-pso-be/node_modules/eslint/lib/linter/node-event-generator.js:290:26)
    at NodeEventGenerator.applySelectors (/Users/rosscoundon/Documents/GitHub/omw-pso-be/node_modules/eslint/lib/linter/node-event-generator.js:319:22)
    at NodeEventGenerator.enterNode (/Users/rosscoundon/Documents/GitHub/omw-pso-be/node_modules/eslint/lib/linter/node-event-generator.js:333:14)

does this

eslintConfig

go into the root/SST package.json, or the package.json for any yarn workspaces?

I believe it works like node modules where you can have it in any and all package.json

I'm seeing a few ECONNRESET issues that I hadn't noticed before when live debugging.

Uncaught Exception      {"errorType":"Error","errorMessage":"read ECONNRESET","code":"ECONNRESET","errno":-54,"syscall":"read","stack":["Error: read ECONNRESET","    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)","    at TCP.callbackTrampoline (internal/async_hooks.js:131:17)"]}
Waiting for the debugger to disconnect...