Registry / testing / eslint-plugin-sitegenesis

eslint-plugin-sitegenesis

JSON →
library1.0.0jsnpmunverified

ESLint plugin with custom rules for Salesforce Commerce Cloud (Demandware) SiteGenesis projects. Current stable version is 1.0.0. This plugin enforces coding standards specific to SiteGenesis cartridge structure and ISML templates. It is a niche tool for Salesforce Commerce Cloud developers, with limited release cadence. Key differentiator: provides linting for SiteGenesis-specific patterns not covered by general ESLint rules.

npm install eslint-plugin-sitegenesis
INSTALL
IMPORT
SIG · ESLINT-PLUGIN-SITE
E
eslint-plugin-sitegenesis
testingjavascriptv1.0.0
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

default
import sitegenesis from 'eslint-plugin-sitegenesis'
const sitegenesis = require('eslint-plugin-sitegenesis')
ESLint plugins are typically required via module.exports in .eslintrc; CJS require works in Node.js.
rules
const { rules } = require('eslint-plugin-sitegenesis')
import { rules } from 'eslint-plugin-sitegenesis'
Rules are exported as a plain object; ESM import may work depending on bundler.
configs
const { configs } = require('eslint-plugin-sitegenesis')
import { configs } from 'eslint-plugin-sitegenesis'
Configs object contains shareable configurations like 'recommended'.

Shows how to configure ESLint to use the plugin with the recommended config and custom rules.

// .eslintrc.json { "plugins": ["sitegenesis"], "extends": ["plugin:sitegenesis/recommended"], "rules": { "sitegenesis/no-direct-dw-usage": "error", "sitegenesis/require-cartridge-path": "warn" } }
Debug
Known issues
gotchaPlugin requires eslint >=3.0.0. Older versions may not load the plugin correctly.
fix
Update eslint to version 3.0.0 or later.
affects: <3.0.0
gotchaRules are prefixed with 'sitegenesis/' in configuration. Omitting the prefix will cause rule not found errors.
fix
Use 'sitegenesis/rule-name' in rules configuration.
affects: >=1.0.0
gotchaNo README data available. Users may need to inspect source code or the plugin's GitHub repository for rule documentation.
fix
Check the package source or open an issue requesting documentation.
affects: >=1.0.0
Errors
Common errors & fixes
ESLint couldn't find the plugin "eslint-plugin-sitegenesis".
Plugin not installed or not in node_modules.
fix
Run 'npm install eslint-plugin-sitegenesis --save-dev'
Definition for rule 'sitegenesis/rule-name' was not found.
Rule name misspelled or not existing in the plugin.
fix
Verify rule names from plugin's source; use correct prefix.
Cannot find module 'eslint-plugin-sitegenesis'
Plugin not installed or module resolution fails.
fix
Ensure plugin is in package.json devDependencies and node_modules exists.
Upgrade
Version history
1.0.0latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
8 hits · last 30 days
node
8
Resources
eslint-plugin-sitegenesis — npm install eslint-plugin-sitegenesis · libregistry