chore: drop dead .npmrc

[ANcpLua]

Drop dead .npmrc — this repo has no package.json, so package-lock=false controls nothing here. The file was template debris.

Reinforced by ANcpLua.NET.Sdk/src/Build/Common/Npm.targets, which explicitly forces --package-lock and npm_config_package_lock=true to override any .npmrc package-lock=false setting in consumer projects:

<!-- Force lockfile generation even if the environment disables it (e.g. package-lock=false in npmrc). -->
<_NpmInstallOptions>--no-fund --no-audit --package-lock</_NpmInstallOptions>

i.e. the framework's own MSBuild logic treats package-lock=false as a misconfiguration to neutralize. Cleaning up the source.

[github-actions]

@coderabbitai autofix

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4e66b9ec-7aad-499c-a82c-f0f9d8366e59

📥 Commits

Reviewing files that changed from the base of the PR and between aa431fd and ef58c94.

📒 Files selected for processing (1)

• .npmrc

Cache: Disabled due to Reviews > Disable Cache setting

Knowledge base: Disabled due to data retention organization setting

---

Behavior Changed

Removed an unused .npmrc configuration file containing package-lock=false. This setting has no behavioral effect in this repository because the project contains no package.json file and does not invoke npm directly—it is a pure .NET-based analyzer project using C# and MSBuild.

Risk Surface

Minimal. The file was inert configuration with no impact:

• No package.json exists to trigger npm configuration parsing
• CI/build pipeline (.github/workflows/ci.yml) uses only dotnet restore and dotnet build; no npm or node invocations present
• The external MSBuild SDK (ANcpLua.NET.Sdk v3.4.34) controls any npm behavior through its Npm.targets module, which explicitly forces --package-lock and npm_config_package_lock=true environment variables that override consumer .npmrc settings
• .gitignore already excludes node_modules/ and package-lock.json, confirming no npm artifacts are tracked

Validation Evidence

• File did not exist in main branch prior to merge, confirming it was template debris
• Project structure is pure C# with .slnx, .csproj, .props, and .targets files; no Node.js project markers
• ANcpLua.NET.Sdk dependency (declared in global.json msbuild-sdks) independently manages any npm orchestration

Generated Artifacts

None. Removal of configuration file does not produce build artifacts.

Cross-Repo Implications

None. Change is localized. The external ANcpLua.NET.Sdk dependency continues to manage npm configuration through its Npm.targets module; consumer repositories using this SDK are unaffected.

Walkthrough

Removes the .npmrc setting package-lock=false, enabling npm to generate and update package-lock.json files during dependency operations.

Changes

Cohort / File(s)	Summary
npm lockfile configuration .npmrc	Removed package-lock=false directive to re-enable npm lockfile generation and maintenance.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• ANcpLua/TourPlanner-Angular#31: Directly conflicts with this change—TourPlanner-Angular#31 adds package-lock=false while this PR removes it.

Suggested labels

area:build

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/drop-dead-npmrc

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/drop-dead-npmrc

• 🛠️ architecture hardening
• 🛠️ security pass
• 🛠️ test gap closure
• 🛠️ docs and changelog alignment
• 🛠️ performance and allocation pass

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Claude encountered an error after 2s —— View job

---

I'll analyze this and get back to you.

[coderabbitai]

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The pull request currently contains no code changes, although the title and description specify the removal of an obsolete .npmrc file. While the repository analysis indicates that the project is 'up to standards', the intended cleanup has not been performed. This gap between the intent and the actual implementation must be resolved before the PR can be considered for merging.

About this PR

• The PR intent is to remove the .npmrc file, but the current diff is empty. Please ensure the file deletion is correctly committed and pushed to the branch.

Test suggestions

• Verify that the removal of .npmrc does not break the build process or npm configurations.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the removal of .npmrc does not break the build process or npm configurations.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}