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

feat: contract in epoch 3.0 #9

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

hugocaillard
Copy link
Collaborator

Important changes for nakamoto;

In the manifest (Clarinet.toml)

[contracts.counter]
path = 'contracts/counter.clar'
epoch = 3.0
clarity_version = 3

In settings/Devnet.toml

epoch_3_0 = 144

stacks_node_image_url = "quay.io/hirosystems/stacks-node:devnet-3.0"
stacks_signer_image_url = "quay.io/hirosystems/stacks-signer:devnet-3.0"
stacks_api_image_url = "hirosystems/stacks-blockchain-api:7.13.1-beta.1"

Make sure to run npm install.
Test the contract in the simnet with npm test and deploy in devnet with clarinet devnet start

@hugocaillard hugocaillard force-pushed the feat/clarity-3-contract branch from ee37671 to 5b8892b Compare August 2, 2024 09:50
@cipherzzz
Copy link

@hugocaillard

# Env 
# wsl2, clarinet v2.8.0, node 18

# Clone repo
git clone [email protected]:hirosystems/clarity-starter.git

# Feature
git checkout  feat/clarity-3-contract

# install dependencies
npm i

# run test
npm run test

failed to load config from /home/cipherz/projects/mechanism/clarity-starter/vitest.config.js

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: (intermediate value).resolve is not a function
    at file:///home/cipherz/projects/mechanism/clarity-starter/node_modules/@hirosystems/clarinet-sdk/dist/esm/node/src/vitest/index.js:43:28
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
    at async loadConfigFromBundledFile (file:///home/cipherz/projects/mechanism/clarity-starter/node_modules/vite/dist/node/chunks/dep-mCdpKltl.js:66365:15)
    at async loadConfigFromFile (file:///home/cipherz/projects/mechanism/clarity-starter/node_modules/vite/dist/node/chunks/dep-mCdpKltl.js:66206:24)
    at async resolveConfig (file:///home/cipherz/projects/mechanism/clarity-starter/node_modules/vite/dist/node/chunks/dep-mCdpKltl.js:65816:24)
    at async _createServer (file:///home/cipherz/projects/mechanism/clarity-starter/node_modules/vite/dist/node/chunks/dep-mCdpKltl.js:62432:18)
    at async createViteServer (file:///home/cipherz/projects/mechanism/clarity-starter/node_modules/vitest/dist/vendor/cli-api.E07AF1Yq.js:10388:18)
    at async createVitest (file:///home/cipherz/projects/mechanism/clarity-starter/node_modules/vitest/dist/vendor/cli-api.E07AF1Yq.js:11736:18)

@cipherzzz
Copy link

@hugocaillard
I was able to deploy the counter.clar contract using clarinet devnet start with the v2.8.0 release - I'm just having trouble with the tests running at this point. The tests were actually working fine for me on v2.7.0 if that is helpful...

@hugocaillard
Copy link
Collaborator Author

Thanks for reporting @cipherzzz
This change probably is the cause.
I'll start to find a fix, in the meantime, would mind trying with Node.js 20?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants