Issues with `next-intl` library

### The issue

Vinext doesn't seem to work with `next-intl`.
I created a brand new NextJS project using `create-next-app`, added the default `next-intl` configuration and default `vinext` setup.
I get the following error when I run the app:

Running the exact same setup with default nextjs works fine.

### Package versions:

| Package | Version |
| ----------- | ----------- |
| vinext | 0.0.15 |
| next | 16.1.6 |
| react | 19.2.4 |
| next-intl | 4.8.3 |

### Possible cause

When I start the vinext dev server, I get the following warning:

`[vinext] next.config option "webpack" is not yet supported and will be ignored`

I assume this is because of the NextJS config injected by the next-intl: `export default withNextIntl(nextConfig);`

Reproduce the reported setup with vinext 0.0.15, Next 16.1.6, React 19.2.4, and next-intl 4.8.3, then compare it with the working default Next.js setup. Inspect how the next.config wrapper from `withNextIntl(nextConfig)` and the `webpack` option are handled. Done means the default next-intl configuration runs under vinext without the reported error.

Written by the indexing model from the issue text.