- Package Name:
@hrica/zcatalyst-cli-plugin-react - Version: 1.0.0
- Type: Scoped package (requires
--access publicon first publish) - Fork Of:
zcatalyst-cli-plugin-reactby Zoho Catalyst Team
- Core functionality implemented (Vite + Webpack adapters)
- Build tool detection working
- Environment variable handling
- Error handling and logging
- All integration tests passing (40 tests)
- Backward compatibility maintained
- README.md updated with fork notice
- CHANGELOG.md with version 1.0.0 details
- FORK-NOTICE.md explaining the fork
- DEPLOYMENT.md with full deployment guide
- QUICK-START-DEPLOY.md for quick reference
- PRE-PUBLISH-CHECKLIST.md for verification
- API documentation in docs/
- Migration guides in docs/
- package.json updated with scoped name
- Version set to 1.0.0
- Description mentions fork
- Keywords include original package name
- publishConfig set to public
- Repository URLs configured
- Files array includes necessary files
- .npmignore excludes test files
- Deployment script for Windows (publish.ps1)
- Deployment script for Linux/Mac (publish.sh)
- Pre-publish hooks configured
- Test scripts working
# 1. Login to npm
npm login
# 2. Verify everything
npm test
npm pack --dry-run
# 3. Publish (first time)
npm publish --access public
# 4. Push to git
git push origin main
git push origin --tags.\scripts\publish.ps1chmod +x scripts/publish.sh
./scripts/publish.shAfter publishing, verify:
- Package on npm: https://www.npmjs.com/package/@hrica/zcatalyst-cli-plugin-react
- Installation works:
npm install @hr/zcatalyst-cli-plugin-react
- Test in a project:
- Create a Vite project and test
- Create a Webpack project and test
- Documentation accessible: README displays correctly on npm
- Git tags pushed: Version tag exists in repository
- This is a fork of the official Zoho Catalyst plugin
- Full credit given to original authors
- Fork notice included in all documentation
- Not officially affiliated with Zoho
- Same MIT license as original
- Requires
--access publicflag for scoped packages - Subsequent publishes don't need the flag
- Can't republish same version number
- Current version: 1.0.0
- Follows semantic versioning
- Use
npm versionto bump versions
- Issues: GitHub repository
- Original plugin: https://www.npmjs.com/package/zcatalyst-cli-plugin-react
- Catalyst platform: https://www.zoho.com/catalyst/
The following files will be published to npm:
@hr/zcatalyst-cli-plugin-react/
├── lib/ # All source code
│ ├── index.js
│ ├── adapters/
│ ├── config/
│ ├── detector/
│ └── utils/
├── docs/ # Documentation
│ ├── api-documentation.md
│ ├── build-tool-detection.md
│ ├── vite-migration-guide.md
│ └── troubleshooting.md
├── README.md # Main documentation
├── LICENSE # MIT license
├── FORK-NOTICE.md # Fork information
├── CHANGELOG.md # Version history
└── package.json # Package metadata
These files are excluded via .npmignore:
- tests/ (all test files)
- .kiro/ (spec files)
- coverage/ (test coverage)
- scripts/ (deployment scripts)
- node_modules/
- Development configuration files
Before publishing, test the package:
# Create a tarball
npm pack
# This creates: hr-zcatalyst-cli-plugin-react-1.0.0.tgz
# Test installation from tarball
mkdir test-install
cd test-install
npm init -y
npm install ../hr-zcatalyst-cli-plugin-react-1.0.0.tgz
# Verify it works
node -e "console.log(require('@hr/zcatalyst-cli-plugin-react'))"If something goes wrong:
-
Deprecate (preferred):
npm deprecate @hr/zcatalyst-cli-plugin-react@1.0.0 "Issue found, use 1.0.1" -
Fix and republish:
# Fix the issue npm version patch npm publish --access public -
Unpublish (last resort, within 72 hours):
npm unpublish @hr/zcatalyst-cli-plugin-react@1.0.0
- ✅ Verify package on npm
- ✅ Test installation
- ✅ Update any external documentation
- ✅ Announce the release
- ✅ Monitor for issues
- ✅ Respond to user feedback
- Maintainer: Harivonjy Rica
- Email: contact.harivonjy@gmail.com
- Repository: https://github.com/h-rica/zcatalyst-cli-plugin-react
- Issues: https://github.com/h-rica/zcatalyst-cli-plugin-react/issues
Ready to deploy! 🚀
Follow the Quick Deploy Commands above or use the deployment script for a guided process.