fix: anchor migrations

[jsonDoge]

Current anchor 0.30.1 doesn't have optional package manager and is hardcoded to use yarn. And to run a migration it simply runs: yarn run ts-node ... {migration stuff} in the cwd.

So when calling a migration from root route, due to package.json existance in anchor folder, it expected a node_modules to exist and call ts-node from there. But due to nx and monorepo structure, it's placed in root. Furthermore nx ignores nested package.json - so simply removing them (anchor/package.json and anchor/package-lock.json) fixes the problem.

After the fix when anchor-migrate is run anchor will place "packageManager": "[email protected]+sha1.1959a18351b811cdeedbd484a8f86c3cc3bbaf72" in root package.json. This is for now ignored and not committed because our current manager is npm and anchor is planning to add support in the next version.

New commands:
npm run anchor-migrate-localnet
npm run anchor-migrate-devnet

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
darklake	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 21, 2024 10:53am

[vitorpy]

Man, Vercel seems very finnicky with this monorepo layout. Minor changes seem to upset it. On the other hand, I think the IDL json file should be shared between the rust code and the web code (it being out of date is a problem), so I kinda like the monorepo idea.

[jsonDoge]

@nx/rollup packages some ts functions from anchor and was using package.json. Would be annoying to keep track of two
package.jsons. It was using package.json for the entry points (and likely dependencies), but since they match the rollup defaults, root package.json without entry points is fine.

Tested preview deployment, works.

P.S. migrations still don't work, but now the problem is in the migration scripts themselves as anchor is now able to call the deploy.ts

[vitorpy]

Oh cool - I'm guessing the scripts running with ts-node need some adaptation to run within anchor migrate.

LGTM.