Joe Harvey
Joe Harvey
To add to what @theiliad said: The vulnerability itself has already been fixed in the color-string library. There's a long chain of node modules that are "upstream" from that module...
@stanislavgeorgiev Does your project currently have a yarn.lock or package-lock.json file in it? If so, then there's no need to fiddle with shrinkwrap. For this case in particular, if `npm...
@thefirstartist Auto-correction on blur would constitute an assumption made by the Carbon team of how a general purpose component is used in certain applications, but not all applications. That is...
@joshblack sweet! What can I do to help out with testing?
If I explicitly reference the index.esm file, I get autocomplete: But if I reference `@carbon/react/icons`, I don't get the auto-complete anymore: If I switch the package.json file in `@carbon/react/icons` to...
When trying the example from their docs, I do indeed get autocomplete, but it looks like they're repo must be broken down into some different folders: Interestingly, I just realized...
For me on Mac, when I stepped into the definitions file it was pulling from, it was in the node modules cache in my typescipt 4.7 directory (`~/Library/Caches/typescript/4.7/node_modules/@types/carbon__icons-react`). I'm guessing...
Confirmed that when I import via `@carbon/react/icons/index.esm`, I get the right set of imports available, which is awesome. The main thing still outstanding for this issue is that I don't...
@metonym unfortunately for my use case I don't believe that would help. The issue I have when working with the icons through the `@carbon/react` export is that the index.js file...