Preserve PACKAGE IMPORT rather than FILE IMPORT while generating final bundle

[jvenki]

I am using vite to create a bundle of a couple of typescript files for production. I use PRODUCTION mode to generate this bundle which is going to be used directly by NodeJS at backend side.

This is my config

export default defineConfig({
    build: {
        lib: {
            entry: resolve(__dirname, "src/framework/express/app.ts"),
            fileName: "app",
            formats: ["es"],
        },
        outDir: "build/express",
        rollupOptions: {
            external: [
                /node_modules/,
            ],
        },
    },
    plugins: [
        // removeMSW(),
        // externalizeDeps({ except: ["express"] }),
    ],
    resolve: { alias: { "@": resolve("src/") } },
});

The generated bundle is perfect except that it has imports with absolute path rather than retaining package imports.

import L from "/Users/abc/Workspace/Programs/fc/lp/node_modules/express/index.js";
import i from "/Users/abc/Workspace/Programs/fc/lp/node_modules/winston/dist/winston.js";

Where fc/lp is the folder which contains the source code from where I am running this vite process.

The problem is that the absolute path is not valid at the place where the build file is going to be deployed and run. How do I ensure that package imports are retained or atleast it uses relative path for accessing node_modules files