Replies: 1 comment 3 replies
-
I think this is similar to #3122 I am concerned about adding more complexity to the resolution of the configuration, because this could trigger a number of recursions which are theoretically infinite. And we know what happened to eslint (aka flat config). I understand the use case a bit (trying to make things generic and reusable, I suppose). Isn't there another alternative? Can't you do what you need with the resources that you have? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It would be great if it would be possible to publish a library with Biome configs, that could extend from each other, e. g:
biome-config (npm module):
configs (folder within module) ->
biome-base.json
biome-esm.json
biome-backend.json
biome-frontend.json
It is already possible to reference in-library configs like this:
However, it doesn't seem possible to extend from a rule that is colocated in the same directory within a package.
E. g. I've tried the following within
biome-backend.json
(located in an NPM module):"extends": ["./node_modules/@kibertoad/biome-config/configs/biome-base.json"],
"extends": ["./biome-base.json"],
"extends": ["biome-base.json"],
None of them seem to work, base seems to be silently ignored without an error.
Beta Was this translation helpful? Give feedback.
All reactions