packageJson

Standardize package.json configurations across repository packages.

1.0k|453|Updated Jun 21, 2017
One-click install
npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill packagejson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: packageJson
Source: https://github.com/forcedotcom/salesforcedx-vscode/tree/main/.claude/skills/packageJson
Command: npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill packagejson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines for maintaining consistent and correct package.json configurations across packages to prevent packaging and dependency issues.

Core Features & Use Cases

  • Enforces naming conventions for non-npm packages and vscode extensions.
  • Documents essential fields and practices for package.json (types, browser, dependencies, devDependencies, packaging).
  • Provides guidance on scripts, dependencies, devDependencies, and packaging workflows, plus vscode contributes tips.
  • Provides linting and validation recommendations to ensure quality and consistency across the repository.
  • Use Case: When adding a new package, consult these rules to ensure naming, packaging, and contributes are correct.

Quick Start

Review every package.json in the repository and align names, dependencies, and packaging settings per these guidelines.

Frequently Asked Questions about packageJson

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize package.json configurations across multiple packages?

Standardize package.json configurations by enforcing naming conventions, browser fields, dependencies, devDependencies, packaging workflows, and vscode contributes rules across all repository packages to prevent dependency issues.

What naming conventions should I use for vscode extensions in package.json?

Use specific repository guidelines for vscode extension package.json naming conventions to distinguish non-npm packages, ensuring correct contributes configurations and preventing packaging issues.

What essential fields should I include in package.json for correct packaging?

Essential package.json fields include types, browser, dependencies, devDependencies, and vscode contributes settings to ensure standardized packaging workflows and prevent dependency issues across repository packages.

How do I validate package.json quality and consistency in a monorepo?

Validate package.json consistency in a monorepo by applying linting recommendations to check naming, packaging, vscode contributes, and the existence of a SKILL.md with name and description frontmatter.

Why do I need a SKILL.md file with frontmatter for my package?

A SKILL.md file with name and description frontmatter validates package compliance with repository guidelines, ensuring proper skill definition alongside optional resource directories like scripts, references, and assets.

When should I consult package.json guidelines for adding a new package?

Consult package.json guidelines when adding a new package to verify naming conventions, browser fields, dependencies, devDependencies, and vscode contributes are correctly configured for consistent packaging.