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

Starknet 0.6.10 Constants Access Issue on final package #1158

Closed
tabaktoni opened this issue Jun 20, 2024 · 1 comment
Closed

Starknet 0.6.10 Constants Access Issue on final package #1158

tabaktoni opened this issue Jun 20, 2024 · 1 comment
Labels
Type: bug Something isn't working

Comments

@tabaktoni
Copy link
Collaborator

Describe the bug

  • constants don't expose StarknetChainId nor any other as const+type exports on the final build
  • Local usage is working (from /src) in the tests.

The imminent conclusion is that namespaced as const+type exports don't get bundled properly.

To Reproduce

import { constants } from "starknet";
const a=constants.StarknetChainId.SN_SEPOLIA;

Expected behavior
Example should pass build

  • Node version [e.g. 21.0.0]
  • Starknet.js version 0.6.10
@tabaktoni tabaktoni added the Type: bug Something isn't working label Jun 20, 2024
@ivpavici ivpavici changed the title Starknet 0.6.10 Constarnts Access Issue on final package Starknet 0.6.10 Constants Access Issue on final package Jun 28, 2024
@jrmncos
Copy link

jrmncos commented Jul 13, 2024

hey! I would like to tackle this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants