Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate ignition-core to v-next #6207

Closed
kanej opened this issue Jan 31, 2025 · 0 comments · Fixed by #6195
Closed

Migrate ignition-core to v-next #6207

kanej opened this issue Jan 31, 2025 · 0 comments · Fixed by #6195
Assignees
Labels
status:ready This issue is ready to be worked on v-next A Hardhat v3 development task
Milestone

Comments

@kanej
Copy link
Member

kanej commented Jan 31, 2025

This is the first step in bringing Ignition into Hardhat 3.
We will do the migration one package at a time, the first will be ignition-core.

TODO

  1. Move the ignition-core files under ./v-next
  2. Update the code to match updated prettier and eslint rules
  3. Re-enable API extractor checks as part of linting
  4. Switch to ESM for the package
    1. Change any code patterns that are implied by this (e.g. switching to dynamic imports)
    2. Update or swap dependencies to work with ESM
  5. Update unit tests (pnpm run test) until all are passing (retaining mocha for the moment)
  6. Update Integration tests (pnpm run test:integrations) until all are passing (retaining mocha for the moment)
@kanej kanej added the v-next A Hardhat v3 development task label Jan 31, 2025
@kanej kanej added this to the Public Alpha milestone Jan 31, 2025
@kanej kanej self-assigned this Jan 31, 2025
@kanej kanej added this to Hardhat Jan 31, 2025
@github-project-automation github-project-automation bot moved this to Backlog in Hardhat Jan 31, 2025
@github-actions github-actions bot added the status:ready This issue is ready to be worked on label Jan 31, 2025
@kanej kanej linked a pull request Jan 31, 2025 that will close this issue
23 tasks
@kanej kanej moved this from Backlog to In Review in Hardhat Feb 4, 2025
@kanej kanej closed this as completed Feb 6, 2025
@github-project-automation github-project-automation bot moved this from In Review to Done in Hardhat Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:ready This issue is ready to be worked on v-next A Hardhat v3 development task
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant