require('css-functions-list') returns "/index.json"

[100terres]

Hi! 🙂

I'm running into an issue where we are not able to load the index.json from the root of this package, because when requiring the package it returns "/index.json" which the right relative or absolute path.

The issue I'm describing happens when using the stylelint@v14.5.0 node API in a jest@v26.6.3 test with node@v14.18.2. (On ubuntu 20.04)

EDIT: It's also uder TypeScript@4.5.5 with babel

stylelint recently added this new function-no-unknown rule which uses under the hood the css-functions-list package here:

• https://github.com/stylelint/stylelint/blob/57bc6ef3917943ed740223055dea9030b142ebc0/lib/rules/function-no-unknown/index.js#L6
• https://github.com/stylelint/stylelint/blob/57bc6ef3917943ed740223055dea9030b142ebc0/lib/rules/function-no-unknown/index.js#L47-L48

It was introduced in this PR

When I execute my code using the function-no-unknown (that was enabled in the stylelint-config-recommended package here) it throws this error

ENOENT: no such file or directory, open '/index.json'

Which is a similar to error raised by someone in the PR stylelint/stylelint#5865 (comment)

I've found a way to make it work using path.resolve instead of the new URL here and directly use the returns of require("css-functions-list") here

Would it make sens to use the path.resolve instead?

[100terres]

Here is where it fails in the codebase
https://github.com/react-forked/dnd/blob/e18cfa53c3f6bb8f085137c934a4a0d9b8332671/test/unit/view/style-marshal/get-styles.spec.ts

Here is the error in CircleCI
https://app.circleci.com/pipelines/github/react-forked/dnd/229/workflows/9d30597b-ac76-4548-b2cb-3416ab0a03fe/jobs/1331

[100terres]

I've also open an issue on the stylelint repo stylelint/stylelint#5904

[niksy]

I think this is related to how Jest handles URL. I could use path.resolve, but using current approach is valid with ESM modules. Please see first if there is something wrong on Jest side.

As for similar issue in Stylelint repo, that issue was solved using URL which, again, is valid approach.

[100terres]

Thank you for your answer and I understand. I've look around a bit and I found that it might also be related to TypeScript (I forgot to mention that I was using it).

• Move to ESM stylelint/stylelint#5291 (comment)
• Concerns with TypeScript 4.5's Node 12+ ESM Support microsoft/TypeScript#46452

Issue following jest ESM support

• Meta: Native support for ES Modules jestjs/jest#9430

[niksy]

@100terres just tried importing module with ESM and CommonJS approach—both work as expected. This is probably something unrelated to how this module exports path to JSON, otherwise this wouldn’t work in Stylelint. README contains example on how to consume JSON file.

Sorry if this isn’t working with you. If there is more reported cases of this "problem", I will see if I can approach this differently (in fact, I can, but I’m trying to follow ESM specification). Otherwise, this stays as it is.

[niksy]

@100terres new version has been published where I’ve changed the way JSON file is resolved, could you try again?

[100terres]

Hi @niksy here's my follow up on this issue in the stylelint repo stylelint/stylelint#5904 (comment)