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

Package.json Issues and Recommendations #661

Open
Riya54671 opened this issue Oct 1, 2024 · 0 comments
Open

Package.json Issues and Recommendations #661

Riya54671 opened this issue Oct 1, 2024 · 0 comments

Comments

@Riya54671
Copy link

1} Private repository: The private field is set to true, which means the package is not intended to be published to the npm registry. However, the repository URL is publicly accessible on GitHub, which may not be intended.

  1. Outdated dependencies: The versions of prettier and turbo are specified, but they may not be the latest versions. It's recommended to use the caret symbol (^) to allow for minor version updates.

  2. Node and pnpm versions: The engines field specifies the versions of Node.js and pnpm, but it's not clear why these specific versions are required. It's recommended to specify a range of versions to ensure compatibility.

  3. Scripts: Some scripts, such as dev, dev:ui, and dev:website, use turbo dev with different filters. It's not clear why these separate scripts are needed, and it may be more efficient to use a single script with optional arguments.

  4. Formatting: The format script uses prettier to format files, but it's not clear why the --write flag is used. It's recommended to use --write only when necessary, as it can lead to unintended changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant