2.0.0-alpha.0: fix global install, modernize toolchain, and ship ESM generator#83
Merged
Conversation
Published packages were missing generators/app/index.js because .npmignore excluded compiled JS and CI published with --ignore-scripts before building. Co-authored-by: Cursor <cursoragent@cursor.com>
ChuckJonas
approved these changes
May 23, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
Replace the split pull-request and ci-pull-request workflows with one pipeline that runs build, test, version checks, and npm publish using current action versions, explicit permissions, and simplified version comparison. Co-authored-by: Cursor <cursoragent@cursor.com>
New projects were still scaffolded with API 44.0, which is far behind current Salesforce releases and causes deploy compatibility issues. Co-authored-by: Cursor <cursoragent@cursor.com>
Remove the duplicate writeNpmPackage merge that overwrote user settings, enable strict TypeScript on the generator, convert tests to TypeScript, and add ESLint, Prettier, and CI quality gates. Co-authored-by: Cursor <cursoragent@cursor.com>
ralphcallaway
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This release prepares generator-ccc v2 as an npm alpha (
2.0.0-alpha.0). It fixes broken global installs, modernizes the generator and CI, and introduces breaking changes that warrant a major bump.npm install -g generator-ccc— Stop excluding compiledgenerators/**/*.jsfrom the published tarball and ensure CI builds before publish soindex.jsis included.yeoman-generatorv7), resolve audit issues, and require Node.js 22 LTS.package.jsonmerge that overwrote user settings; default new manifests to API 60.0 (was 44.0).npm link/watchworkflow documented in README.Breaking changes (v2 alpha)
>=22required (see.nvmrc).package.xmlAPI version is 60.0 for new projects.update-notifierremoved.Version & publish
2.0.0-alpha.0inpackage.jsonandpackage-lock.json.master, CI publishes to npm with dist-tagalpha(npm install -g generator-ccc@alpha).latestis unchanged until a stable2.0.0release.Test plan
npm ci && npm run build && npm run typecheck && npm run lint && npm run format && npm testnpm linklocally, runyo cccin a test SFDX project (fresh and existing fixtures)package.json/.prettierrc/ VS Code settings are merged, not overwrittennpm view generator-ccc@alpha versionis2.0.0-alpha.0npm install -g generator-ccc@alphaand runyo cccglobally