config.yml has not been the standard since Grakkit v5. package.json is the standard and will be going forward!

I don't agree with this.

That violates our second principle, as we're making this suddenly opinionated.
package.json is not a graal-specific item, it is a product produced by NodeJS.
Grakkit doesn't support NodeJS at the moment, so requiring a package.json becomes immediately misleading.

What happens when the user wants to use Deno, which is a NodeJS alternative?

What about when package.json makes significant schema changes?

Or what happens when the user doesn't want to use package.json for plugin configurations, to minimize the amount of noise?

How about when we need to extend additional customizations onto our config?

Or the user has a need to have main property within package.json point to something else? Do they now need multiple package.json? Users could run into issues with workspaces due to this.

A good portion of our users right don't use a single method. Everyone does something different.

I propose that instead of making package.json the standard, we give the users the option.

Grakkit-specific configuration can be driven by .grakkitrc, package.json, modules.json, or anything else.

Support needed for multiple config file formats! #33

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions