vfile/do-not-use-conditional-minpath after 0.5.3 -> 0.6.1

[linonetwo]

 FAIL  test/list.test.mjs
  ● Test suite failed to run

    Cannot find module 'vfile/do-not-use-conditional-minpath' from 'dist/index.mjs'

      at Resolver.resolveModule (node_modules/.pnpm/jest-resolve@27.5.1/node_modules/jest-resolve/build/resolver.js:324:11)

Test Suites: 14 failed, 14 total
Tests:       0 total
Snapshots:   0 total
Time:        2.344 s

don't know why, can't search for this.

My usage is simple

import { unified } from 'unified';
import remarkParse from 'remark-parse';
import { VFile } from 'vfile';
import retidStringify, { IOptions } from './retid-stringify';
import { Root as MdastRoot, Content as MdastContent } from 'mdast';

export const md2tidProcessor = unified().use(remarkParse).use(retidStringify);

export async function md2tid(markdownString: string): Promise<string> {
  const vFile = new VFile({ path: 'fileName', value: markdownString });
  const file = await md2tidProcessor.process(vFile);
  return file.value as string;
}

export function toString(value: MdastRoot | MdastContent | string, options: IOptions) {
  if (typeof value === 'string') {
    value = { type: 'paragraph', children: [{ type: 'text', value }] };
  }

  if (value.type !== 'root') {
    value = { type: 'root', children: [value] };
  }

  return unified().use(retidStringify, options).stringify(value);
}

[linonetwo]

Found it on bundled file, but don't know why

import { decodeString as decodeString$1 } from 'micromark-util-decode-string';
import { toString as toString$2 } from 'mdast-util-to-string';
import { ok } from 'devlop';
import { path } from 'vfile/do-not-use-conditional-minpath';
import { proc } from 'vfile/do-not-use-conditional-minproc';
import { isUrl, urlToPath } from 'vfile/do-not-use-conditional-minurl';

[wooorm]

Sounds like you need to fix your bundler. This should work

[ChristianMurphy]

Adding on the stack trace includes jest.

jest-resolve@27.5.1/node_modules/jest-resolve/build/resolver.js:324:11

Jest is known to have problems with ES modules (ESM). They have experimental ESM support https://jestjs.io/docs/ecmascript-modules but it has been experimental for years and has known bugs.

Consider dropping Jest entirely if you can, there are alternatives like node:test and vitest which do fully support ESM.
Or you could wrap jest with another tool like vite https://hung.dev/posts/jest-vite

[linonetwo]

Okay, I did spend some time make rollup + jest work with esm. I will switch to vite to see if it works.

[alankalb]

If you are stuck using jest, you will need to add entries to the moduleNameMapper in jest config to point jest to the absolute path for these files:

moduleNameMapper: {
    ...,
    "vfile/do-not-use-conditional-minpath": "<rootDir>/node_modules/vfile/lib/minpath.browser.js",
    "vfile/do-not-use-conditional-minproc": "<rootDir>/node_modules/vfile/lib/minproc.browser.js",
    "vfile/do-not-use-conditional-minurl": "<rootDir>/node_modules/vfile/lib/minurl.browser.js",
  },

[linonetwo]

Thanks