Itamar Gronich
Itamar Gronich
### pnpm version: 7.5.2 ### Code to reproduce the issue: use node 17.9.1 and pnpm 7.5.2 https://github.com/ItamarGronich/pnpm-bug-child-concurrency ### Expected behavior: child-concurrency is parsed as number and not a string ###...
### Desired behavior Foundation runs on latest node versions (16, 17) ### Current behavior Foundation runs on node version no greater than 10. ### This raised a question Why does...
### Problem documentation on global variables: https://get.foundation/emails/docs/global.html#sass-variables It shows that you can use `$global-gutter-small` but it's only in the `develop` branch and not yet in any release. Also, docs say...
### Checkboxes for prior research - [X] I've gone through [Developer Guide](https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide) and [API reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest) - [X] I've checked [AWS Forums](https://forums.aws.amazon.com) and [StackOverflow](https://stackoverflow.com/questions/tagged/aws-sdk-js). - [X] I've searched for [previous similar...
* [x] Are you running the latest version? * [x] Have you included sample input, output, error, and expected output? * [x] Have you checked if you are using correct...
Typescript with module resolution "NodeNext" + type: "commonjs" fails to import the commonJS module
## Description When using with `packageJson.type = 'commonjs'` (the default) and typescript with the following config: ``` { "compilerOptions": { "module": "NodeNext", "moduleResolution": "NodeNext", "esModuleInterop": true } } ``` `tsc`...
Resolves https://github.com/lucaong/minisearch/issues/255 Hey @lucaong, I hope this is the direction you were hoping for. It's just the simplest least intrusive change i could think of. Let me know if there...
### Search Terms exports, package.json, tsconfig, extends, base config ### Description While tsc works and resolves the config files from the exports fields of the packages, ts-node fails. ### Expected...
Does chrome intent to fix this? is there a CVE or bug on the chrome project for this?