export deweb-cli functions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently, when importing deweb-cli functions from another repo (expl deweb-uploader) we use full path. expl:
import { Metadata } from "@massalabs/deweb-cli/bin/lib/website/models/Metadata";
We should be able to import every deweb-cli exported function directly from the npm package name :
import { Metadata } from "@massalabs/deweb-cli"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating deweb-cli's public package entry point and current export declarations, then inspect how the npm package is built and packaged. Done means Metadata and the other intended exported functions can be imported directly from @massalabs/deweb-cli instead of using bin paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100