Victor van Poppelen

I have a working implementation for a package defining `"type": "module"`, and using a `.js` configuration file: https://github.com/davidtheclark/cosmiconfig/compare/v7...vvanpo:type-module Here's an example usage: @coreyfarrell it's using your `get-package-type` utility, works flawlessly....

One problem I'm foreseeing is that once https://github.com/nodejs/node/issues/31860 lands and we're able to run tests against `loadMjs()` using `node --experimental-vm-modules node_modules/.bin/jest`, this will only work on the latest `node` release....

I suppose we could pull the Jest configuration out of the `package.json` and into a `jest.config.js` file, and then only enforce coverage on `node` versions greater than 10.

@just-boris it's not really Jest's fault, they're waiting on Node.js to sort out module support for their `vm` API, which is apparently causing them some trouble. So while we could...

@zeroarst your `devDependencies` lists `vue-jest` as using version `^1.0.2`, but at the time of your posting version 3 had already been out for a year. I'm not sure if upgrading...

The `babelConfig` option was removed entirely in https://github.com/vuejs/vue-jest/releases/tag/v4.0.0-beta.0 So I think we need to remove all references of it in the README.md.

@cebe even though the JavaScript dependency is not included in the release tarball, the presence of the `yarn.lock` file causes security scanning tools like Snyk to report a critical vulnerability...

@znck can you shed some light on this issue, and any potential workarounds? I get the exact same `Can't find stylesheet to import.` error on all of my Sass imports...

After a bit of digging I've learned that importing `node_modules` is not actually something `sass` supports out-of-the-box. I was using the `~@some/package` syntax, having assumed that `~` was particular to...

@khalyomede a quicker fix would be to run `SASS_PATH=node_modules rollup -c`, which I can confirm works.