[Bug]: Themes depend on @resume/core instead of @jsonresume/core

[TheComputerM]

Bug Description

Take for example jsonresume-theme-academic-cv-lite. I can't install it locally because the dependency "@resume/core" doesn't exist. It was replaced but the new packages aren't pushed to npm.

Steps to Reproduce

1. Go to https://www.npmjs.com/package/jsonresume-theme-academic-cv-lite?activeTab=dependencies
2. Click on the dependencies tab
3. Click on the @resume/core dependency

Expected Behavior

New package dependency change should be pushed to npm

Actual Behavior

Old dependency remains

Screenshots

No response

Severity

Critical (blocks major functionality)

Environment

Error Logs

Additional Context

No response

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• [Bug]: missing @resume/core@0.1.0 #245

Related Issues

• CommonJS builds of themes in ./packages #152
• CI Build Failures: Module Resolution and ESLint Configuration Errors #240
• [Bug]: date don't show correctly in a theme that hasn't been updated for 4 years #250

🔗 Related PRs

#102 - adding ability to auth with github (stateless) that allows you to create and edit gist [WIP] [merged]
#136 - Enhance project structure with new configuration options and UI components [merged]
#159 - prevent version bumps from dependency [merged]

👤 Suggested Assignees

• thomasdavis
• mi-ar-82
• XuluWarrior
• dolanor
• levino

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[elyday]

https://www.npmjs.com/package/jsonresume-theme-modern-classic is also effected by this.

I saw that it was changed in the code but it was not published to the npm registry.

[mardukbp]

As a workaround you can refer to the package by an alias, as suggested in a previous issue. In your package.json add:

    "@resume/core": "npm:@jsonresume/core@^0.1.0"