Preventing "require" statement from being generated for external dependencies

[mysticfall]

I'm using the following config file to build my application targeted for Node.js.:

import {defineConfig} from "vite"
import tsconfigPaths from "vite-tsconfig-paths"
import nodeExternals from "rollup-plugin-node-externals"

export default defineConfig({
    plugins: [tsconfigPaths(), nodeExternals()],
    build: {
        rollupOptions: {
            input: "src/index.ts",
            output: {
                entryFileNames: "my-plugin.js",
                format: "cjs",
                dir: "dist",
                globals: {
                    skyrimPlatform: "skyrimPlatform"
                }
            },
            external: ["skyrimPlatform"]
        }
    }
})

My intention is to exclude skyrimPlatform from the dependency list since it will be globally available at runtime. However, it still generates the require statement for the module like this:

const skyrimPlatform = require('skyrimPlatform'); // I want this line to be removed,
const os = require('node:os'); // while keeping this.

//...

from this source script:

import {Debug, Game, once, printConsole} from "skyrimPlatform"
import os from "node:os"

//...

The only way I could make it omit the require statement is by changing the format to umd or iife, but it broke importing native Node modules like os:node.

Is there a way I could achieve this?

Thanks!

[hi-ogawa]

Probably swapping it via virtual module works fine, something like:

export default defineConfig({
  plugins: [myPluign()]
})

function myPluign() {
  return {
    name: 'my-plugin',
    enforce: 'pre',
    resolveId(source) {
      if (source === 'skyrimPlatform') return '\0skyrim'
    },
    load(id) {
      if (id === '\0skyrim') {
        // assuming this list isn't too huge or can be auto-generated somehow
        return `
export const Debug = skyrimPlatform.Debug;
// ...
`
      }
    }
  }
}

[mysticfall]

Probably swapping it via virtual module works fine, something like:

export default defineConfig({
  plugins: [myPluign()]
})

function myPluign() {
  return {
    name: 'my-plugin',
    enforce: 'pre',
    resolveId(source) {
      if (source === 'skyrimPlatform') return '\0skyrim'
    },
    load(id) {
      if (id === '\0skyrim') {
        // assuming this list isn't too huge or can be auto-generated somehow
        return `
export const Debug = skyrimPlatform.Debug;
// ...
`
      }
    }
  }
}

Thanks for the answer. I'm not sure if I understood you correctly, though. Wouldn't it make the transformation fail with errors like this?

src/index.ts (1:21): "once" is not exported by "skyrim", imported by "src/index.ts".

1: import {Debug, Game, once, printConsole} from "skyrimPlatform"
                        ^

The skyrimPlatform module (aliased from @skyrim-platform/skyrim-platform) exports type definitions against which the project is built. So, wouldn't replacing it with a virtual module force me to export every referenced symbol by hand?

It's a framework-type module, and I'm referencing it via yet another library, so I'm not sure if it'd be a viable option for me.

[mysticfall]

Using rollup-plugin-external-globals plugin has solved my issue.