Dmitriy Fuks

https://github.com/borisdiakur/memoize-fs/blob/1414391cd3c5498e6bc848044be85b592c71ac1d/src/index.ts#L32 As I understand, the problem arises here. A repeated reference to an object is identified as a cyclical reference. But this is not entirely accurate. There is no cyclical...

@mrginglymus Thanks! This workaround works. However, for it to work with workspaces, you also need to add the following code to `.yarnrc.yml`: ```yml packageExtensions: "@storybook/test@*": peerDependencies: "@storybook/core": "*" ```

I think this is a bug on the `@storybook/test` side. It references `@storybook/core`, so it should have it in its `peerDeps`.

@kondo0602 Be careful. By overriding the `compilerOptions.types` field, you change the default behavior for global types. For example, `@types/node` types will no longer be added to the global type scope....

Hi! There is a [vulnerability in the cookie library](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), which was fixed in version 0.7.0. Unfortunately, in the import-map-overrides library, the cookie version is specified as ^0.6.0, which does not...

@rodion-sarakuz As a workaround, I managed to pass the parameter `markers: []` during map initialization. This is related to the following line of code: [https://github.com/themustafaomar/jsvectormap/blob/5f771865c3ecbad755ad9248afde0e473e5bf893/packages/jsvectormap/src/js/map.js#L88-L91](https://github.com/themustafaomar/jsvectormap/blob/5f771865c3ecbad755ad9248afde0e473e5bf893/packages/jsvectormap/src/js/map.js#L88-L91)"**

I encountered a [similar problem](https://github.com/swc-project/plugins/issues/261) related to upgrading `@swc/core` to version 1.3.106. I am developing an external library and cannot force all consumers to specify resolutions in package.json :( It...

@ArnaudBarre I'm developing a library-bundler based on Vite, which is used for building frontends within our company. It has the following dependencies: ```json "@swc/plugin-styled-components": "1.5.116", "@vitejs/plugin-react-swc": "3.5.0", ``` We use...

I don't see anything wrong with loading 2 versions of `@swc/core` - one just won't be used. Library users install it with a simple command `yarn add @my-org/frontend-scripts`. In this...

Perhaps you misunderstood me. We don't use Vite for library builds. It's used as part of our internal library for building Vite-based applications. But alright. I got you - I'll...