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.

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

(feat) Specify tooling used in package.json #221

Open
1 task done
eirnym opened this issue Jan 22, 2025 · 3 comments
Open
1 task done

(feat) Specify tooling used in package.json #221

eirnym opened this issue Jan 22, 2025 · 3 comments
Labels
enhancement New feature or request
Milestone

Comments

@eirnym
Copy link

eirnym commented Jan 22, 2025

Does it fit the projects scope?

  • This is relevant

Why?

Package.json file has option to specify tooling and their supported version ranges (specifically engines section). Please, do this. I can read .github/workflows/publish.yaml, but this section is quite easier to read

Solution?

engine section in package.json file.

Alternatives?

read workflow yaml file.

Extra Context

No response

@eirnym eirnym added the enhancement New feature or request label Jan 22, 2025
@enchant97
Copy link
Owner

Sure. I thought I had already done this, I guess not.

Currently the frontend requires node >=v20 and uses npm for package management, although this will be changing soon (to pnpm).

@eirnym
Copy link
Author

eirnym commented Jan 24, 2025

Do you use or plan to use corepack?

@enchant97
Copy link
Owner

I use nix. It should not matter where the user has installed node & package manager from as long as the versions meet the requirements.

@enchant97 enchant97 moved this to Todo in Note Mark Mar 4, 2025
@enchant97 enchant97 added this to the V0.16.x milestone Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

2 participants