Valentinas Janeiko

Installing `@material/*` manually can be avoided by adding `public-hoist-pattern[]=@material/*` to `.npmrc`, but this is still a workaround. (and you still need to explicitly add `node_modules` folder to include paths: `-i...

This seems to work: https://nodejs.org/docs/latest-v16.x/api/packages.html#subpath-exports ```js // tsconfig.json ... "paths": { "#Src/*": [ "./src/*" ] }, ... // package.json ... "imports": { "#Src/*": "./dist/*" } ... // ./src/index.ts import {...

Was just reporting a bug. I am currently using this workaround: ```ts z.object({}).catchall(z.boolean()) as z.ZodObject< z.ZodRawShape, 'strip', z.ZodBoolean, Record > ```

@colinhacks wouldn't intersecting an index signature with an object capture the semantics of `.catchall()`? ```tsx type X = { x: number } & { [key: string]: boolean }; type Q1...

`"wrapperLength":77` Here is the full `JSON.stringify()`: ```json { "sourceMap": {"version":3,"file":"/workspace/src/utils/function.ts","names":["noop","noopSync","Promise","resolve"],"sources":["/workspace/src/utils/function.ts"],"sourcesContent":["export const noop = () => Promise.resolve();\nexport const noopSync = () => {\n /* noop */\n};\n"],"resolvedSources":["/workspace/src/utils/function.ts"],"_encoded":"AAAA;;;;;;;;;;;IAAaA,IAAI,MAAJA;IACAC,QAAQ,MAARA;;AADN,MAAMD,OAAO,IAAME,QAAQC,OAAO;AAClC,MAAMF,WAAW,IAAM;AAC5B,QAAQ,GACV","_decoded":[[[0,0,0,0]],[],[],[],[],[],[],[],[],[],[],[[4,0,0,13,0],[8,0,0,17],[14,0,0,13,0]],[[4,0,1,13,1],[12,0,1,21],[18,0,1,13,1]],[],[[0,0,0,7],[6,0,0,13,0],[13,0,0,20],[17,0,0,26,2],[25,0,0,34,3],[32,0,0,41]],[[0,0,1,7],[6,0,1,13,1],[17,0,1,24],[21,0,1,30]],[[0,0,2,2],[8,0,2,10],[11,0,3,0]]],"_decodedMemo":{"lastKey":5,"lastNeedle":0,"lastIndex":-1}}, "startCol": 263, "endCol": 271, "this":...

Previously I sent `this` from `offsetToOriginalRelative`, that's way it wasn't there. Here is `this` from `_maybeRemapStartColEndCol`: ```json {"path":"/workspace/src/utils/function.ts","wrapperLength":77,"sources":{"originalSource":"export const noop = () => Promise.resolve();\nexport const noopSync = () => {\n...

Dosn't really matter. Just a simple hello world reproduces the issue. ```js "use strict"; function main() { console.log('Hello, World!'); } void main(); ```

The typo was only in the GitHub issue, not the command I was running. Sorry about that. I will create a repo to reproduce it later today.

Here is the repo that reproduces the issue: https://github.com/valeneiko/clinic-bug I couldn't reproduce the issue initially either, but `pnpm audit --fix`, made it fail like described. I think it's the fact...

I added equivalent `npm` lockfile, it is now reproducible with `npm` too: https://github.com/valeneiko/clinic-bug