Henry Cai

In my own experience, next-logger doesn't work with Winston out of the box even though the doc has instructions to do so. There are multiple issues: 1. The logger export...

Starting from Next 14.2, @GAsplund's solution above won't work in the Next **development mode** (`next dev`), the generated Webpack instrumentation code won't include `next-logger`. Combining @karl-run's solution to add `next-logger`...

@ayusharma @byara Could someone please review https://github.com/trivago/prettier-plugin-sort-imports/pull/293 or https://github.com/trivago/prettier-plugin-sort-imports/pull/273?

Finally find out a workaround for the module loading problem starting from 14.2, see https://github.com/sainsburys-tech/next-logger/issues/13#issuecomment-2113625702

I have verified that with `v5.0.0`, we don't need to set `next-logger` in `experimental.serverComponentsExternalPackages` as mentioned in https://github.com/sainsburys-tech/next-logger/issues/13#issuecomment-2113625702. And this issue was originally about using `next-logger` in the standalone mode,...

Hi, when could we expect this to be merged and released? Using custom decorators with RSC seems to be broken and needs to be fixed by this, otherwise I am...

@shilman Maybe related to https://github.com/vitest-dev/vitest/issues/6187? To add more context for my use case: I also have client and server code in a Next.js project, and I would like to share...

Just to share a workaround for Typescript users until we figure out how to type the configs properly ```javascript // @ts-expect-error https://github.com/jsx-eslint/eslint-plugin-react/issues/3878 reactPlugin.configs.flat.recommended, ```

@3dos There were two attempts to fix this issue, #3879 and #3882, #3879 was taking the same approach as yours and it didn't work due to https://github.com/jsx-eslint/eslint-plugin-react/pull/3879#discussion_r1915506808, you could try...

The dependency `node:url` has been removed (https://github.com/salesforce/tough-cookie/pull/480) in v5.1.0