User provided rollup plugin no longer recognized by snowpack. Breaks build. 3.0.13 -> 3.1.2

[manzt]

I have a snowpack project (v3.0.13) that uses a custom rollup plugin to ignore a difficult child-dependency since it's exports aren't used in the final build. In v3.1.2, it seems the plugin hooks I am using (load) are either ignored by snowpack or other plugins take precedent, breaking my previous build.

The example below demonstrates this behavior. It seems that myPlugin.load is never called in v3.1, so I can't resolve the import manually.

// index.js
import confetti from 'canvas-confetti';
console.log(confetti);

// snowpack.config.js
const myPlugin = () => {
  return {
    id: 'log-id',
    load(id) {
      console.log(id); // just logs the file id
      return;
    }
  }
}

/** @type {import("snowpack").SnowpackUserConfig } */
module.exports = {
  packageOptions: {
    rollup: {
      plugins: [ myPlugin() ]
    }
  },
};

v3.0.13

$ npm run build

> @ build /Users/manzt/demos/test-rollup-plugin
> snowpack build

[snowpack] ! building source files...
[snowpack] ✔ build complete [0.07s]
[snowpack] ! building dependencies...
/Users/manzt/demos/test-rollup-plugin/node_modules/canvas-confetti/dist/confetti.module.mjs
[snowpack] ✔ dependencies ready! [0.11s]
[snowpack] ! verifying build...
[snowpack] ✔ verification complete [0.00s]
[snowpack] ! writing build to disk...
[snowpack] watching for changes...

v3.1.2

$ npm run build

> @ build /Users/fm813/demos/test-rollup-plugin
> snowpack build

[11:25:46] [snowpack] ! building files...
[11:25:46] [snowpack] ✔ files built. [0.02s]
[11:25:46] [snowpack] ! building dependencies...
[11:25:46] [snowpack] ✔ dependencies built. [0.19s]
[11:25:46] [snowpack] ! writing to disk...
[11:25:46] [snowpack] ✔ write complete. [0.01s]
[11:25:46] [snowpack] ▶ Build Complete!

Is there any documentation regarding this change, or a description of what behavior to expect for user provided plugins? I'd just like to tell snowpack (moreover esinstall) to ignore a dependency of a dependency since it contains node-js builtins and is never used in my app:

// node_modules/some-package/index.js
import { anUnusedFunction } from "some-nodejs-dependency-i-want-to-ignore-completely";
// just want a rollup plugin to resolve this dependency to `export const anUnusedFunction = () => {};`

export function a() {
  anUnusedFunction();
}

export function b() {
  // just javascript
  /* ... */
}

// index.js
import { b } from "some-package";
/* ... */