Alright, as soon as I opened an issue, had an idea... (of course!) 💡 😁

I was actually using a loaded plop file from the main file, and that is what triggered this bug!

So it looks like force is not being applied to loaded plopfiles.

plopfile.ts

import type { NodePlopAPI } from 'plop';

module.exports = async function (plop: NodePlopAPI) {
  await plop.load('./name.ts')
};

name.ts

import type { NodePlopAPI } from 'plop';

module.exports = function (plop: NodePlopAPI) {
  plop.setGenerator('test', {
      description: 'This is loaded.',
      prompts: [{
        name: 'name',
        message: 'What is your name?',
        type: 'input',
      }],
      actions: [
        {
          type: 'add',
          template: 'foo {{name}}',
          path: 'foo-bar',
        }
      ]
  });
};

That clarification is extremely helpful. Lemme see if I can take a stab at finding the root cause

I think this is because we don't inherit any of the parent config props from our load method:

https://github.com/plopjs/plop/blob/main/packages/node-plop/src/node-plop.js#L102-L107

I could be wrong, but I think if we simply changed the const config lines to:

    const config = Object.assign(
      plopCfg,
      {
        destBasePath: getDestBasePath(),
      },
      loadCfg
    );

It would fix this bug.

Any chance you wanna pull it down, test my theory, maybe write a test to validate this fix, and make a PR? 😊

Your fix does indeed work! :)

FYI I am working on a PR.

BTW @moltar I deeply appreciate you having opened a PR. I'm working on TS support given our botched 4.0 release right now, but I will address your fix soon there after :)