Getting 404 when using localeSubpaths and next-route for dynamic routing

Hi, I am not sure if it is my setup issue or the 2 packages are conflicting…

I have a product.js under pages/ directory I am support 2 languages with these pattern

/product/1
/zh/product/1

However, only the default route (en) works This is my setup

routes.js

const routes = require('next-routes');

module.exports = routes()
    .add({
        name: 'product',
        pattern: '/(zh)?/product/:id',
        page: 'product',
    });

i18n.js

const NextI18Next = require('next-i18next');

module.exports = new NextI18Next({
    otherLanguages: ['zh'],
    defaultLanguage: 'en',
    localeSubpaths: true,
});

server.js

const express = require('express');
const next = require('next');
const nextI18NextMiddleware = require('next-i18next/middleware');

const nextI18next = require('./i18n');
const routes = require('./routes');

const app = next({ dev: process.env.NODE_ENV !== 'production' });
const handler = routes.getRequestHandler(app);
const server = express();

app.prepare()
    .then(() => {
        nextI18NextMiddleware(nextI18next, app, server);
        server
            .use(handler)
            .listen(3000, (err) => {
                if (err) {
                    // eslint-disable-next-line no-console
                    console.error('err', err);
                }
            });
    });

I have read the documentation of both pacakges and tried lots of combination for routes.js, but still can’t make it work. Am I doing this correctly?

[wk93]

I passed next-routes request handler function into next-i18next middleware and I think it works.

(async () => {
  const app = next({ dev: process.env.NODE_ENV !== 'production' })
  const handler = routes.getRequestHandler(app)

  await app.prepare()
  const server = express()

  nextI18NextMiddleware(i18next, { render: handler }, server)

  server.get('*', (req, res) => handler(req, res))

  await server.listen(3000)
  console.log('> Ready on http://localhost:3000')
})()

[isaachinman]

Closing due to lack of activity, happy to reopen this at any time. I would imagine that @wk93’s approach probably works.