| name | evernote-upgrade-migration |
| description | Upgrade Evernote SDK versions and migrate between API versions.
Use when upgrading SDK, handling breaking changes,
or migrating to newer API patterns.
Trigger with phrases like "upgrade evernote sdk", "evernote migration",
"update evernote", "evernote breaking changes".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| compatible-with | claude-code, codex, openclaw |
| tags | ["saas","evernote","api","migration"] |
Evernote Upgrade & Migration
Current State
!npm list evernote 2>/dev/null || echo 'evernote SDK not installed'
Overview
Guide for upgrading Evernote SDK versions, converting callback-based code to Promises, handling breaking changes, and maintaining backward compatibility during gradual migration.
Prerequisites
- Existing Evernote integration to upgrade
- Test environment for validation
- Understanding of current implementation patterns
Instructions
Step 1: Check Current Version
Identify your current SDK version and compare against the latest release. Check the changelog for breaking changes between versions.
npm list evernote
npm view evernote version
npm view evernote repository.url
Step 2: Review Breaking Changes
Common breaking changes across Evernote SDK versions:
- Constructor changes:
new Evernote.Note() became new Evernote.Types.Note()
- Callback to Promise: Older versions used callbacks, newer versions return Promises
- Import path changes: Module structure may change between major versions
- Thrift version updates: Underlying Thrift protocol may change serialization
Step 3: Convert Callbacks to Promises
Wrap callback-based SDK calls in Promise wrappers for modern async/await usage.
noteStore.getNote(guid, true, false, false, false, (error, note) => {
if (error) return handleError(error);
processNote(note);
});
const note = await noteStore.getNote(guid, , , , );
(note);
