Guillaume Mathieu

I spent all day figuring out why my code was compiled twice and found that karma re-registers `ts-node`. My only path forward was to register and replace it with a...

@blakeembrey karma's config parser [automatically registers `ts-node`](https://github.com/karma-runner/karma/blob/7617279f68507642fdc7eb0083916f3c6c2a28cb/lib/config.js#L37) in order to support `karma.conf.ts`. Not much we can do about it other than overriding `require('ts-node').register = function() {}`. Thanks for following up.

Hi everyone, Here's a [PR](https://github.com/skovy/typed-scss-modules/pull/225) with a fix. 🤞

I've run into the same issue. Within the source file, the deprecation is properly reported: ```ts export interface DialogHeaderProps { /** @deprecated use children instead. */ heading?: string } const...

I was able to get basePath working with the following workaround: ```ts // src/app/api/auth/[...nextauth]/route.ts import { NextRequest } from 'next/server' import { handlers } from '@/auth/auth' import { basePath }...

I can confirm that the tunnel only works for **the personal stage**. I tried downgrading to previous versions, `3.11.21` and `3.9.4`, running `sst refresh`, without luck. Help would be greatly...

I found a workaround by tunneling to your personal stage. The trick is to deploy your personal stage that points to the same VPC used in the production stage. Here's...