Skip to content

Possible module cache bug #114

@olsonpm

Description

@olsonpm

I expect the module cache to be used for ./dep2.mjs in the following case.

repro code
// dep1.mjs
export default {}


// dep2.mjs
export default {}


// run.mjs
import quibble from 'quibble'
import dep1 from './dep1.mjs'
import dep2 from './dep2.mjs'

await quibble.esm('./dep1.mjs', {}, { mockDep1: true })

const dep2After = await import('./dep2.mjs')

console.log('dep2 === dep2After: ' + (dep2 === dep2After))
// logs "dep2 === dep2After: false"
to reproduce from my branch
$ git clone 'git@github.com:olsonpm/repro.git'
$ cd repro
$ git checkout quibble-show-module-cache-bug
$ npm ci
$ node run.mjs

# logs "dep2 === dep2After: false"

is this expected behavior for some reason ? Or is this a regression of testdouble #492 ?

I'm willing to dig in if this is confirmed a bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions