Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Finishing civetconfig #1239

Open
4 of 8 tasks
edemaine opened this issue May 9, 2024 · 1 comment
Open
4 of 8 tasks

Finishing civetconfig #1239

edemaine opened this issue May 9, 2024 · 1 comment

Comments

@edemaine
Copy link
Collaborator

edemaine commented May 9, 2024 •
edited
Loading

  • VSCode extension uses default civetconfig
  • CLI uses default civetconfig
  • unplugin should support default civetconfig, along with config override
  • eslint plugin should probably do the same
  • Babel plugin should probably do the same
  • Gulp plugin should probably do the same
  • What about ESM and Bun plugins?
  • Document in https://civet.dev/config
@edemaine edemaine mentioned this issue May 10, 2024
Merged
@danielbayley danielbayley mentioned this issue Jun 30, 2024
Merged
@danielbayley
Copy link
Contributor

danielbayley commented Jun 30, 2024 •
edited
Loading

There are also the proposed potential config files, as @STRd6 mentioned in #647 (comment).

Allow for parsing different config file extensions based on what modules exist in the local user project

Plus I threw together a quick PR to allow civetConfig in package.json also in #1300.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edemaine @danielbayley