GoogleChrome / GoogleChrome/chrome-extensions-samples

Proposal: Enforce Node Version Rule and Prevent Modifications to package-lock.json

Open
#1,130 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
17.8k
Forks
9k
Avg merge
21h
Merged PRs (30d)
28

Description

**Describe the bug**
Currently, there is no established rule regarding the required Node.js version for this project. Additionally, modifications to the package-lock.json file are occurring despite the absence of a defined policy.

**To Reproduce**
Steps to reproduce the behavior, or file the issue is found in:

1. Attempt to determine the required Node.js version for the project.
2. Observe inconsistent modifications to the package-lock.json file.

**Expected behavior**
We should establish a clear rule specifying the required Node.js version for this project to ensure consistency among contributors. Furthermore, we need to enforce a policy to prevent modifications to the package-lock.json file, maintaining project stability and consistency.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing package-lock.json and the project's current Node.js requirements, then determine how dependency-file changes are currently managed. Done means the required Node.js version and a clear policy preventing unintended package-lock.json modifications are documented and enforced.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
build-system, developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.