ipfs-shipyard / ipfs-shipyard/ipfs-dag-builder-vis
dag.ipfs.io: Source map shipped @Prod
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Originally opened by @pranshuchittora in https://github.com/ipfs/website/issues/407 ... quoted below:
Hi, I am not able to find the repo for the dag.ipfs.io so opening the issue here.
While tinkering with the DAG I found out that the source maps are being shipped @Prod.
Just CRA things :)
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 the create-react-app production build configuration for dag.ipfs.io and confirm how source maps are generated and deployed. Reproduce or inspect a production build, then verify that the deployed assets no longer ship source maps while the application still builds successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100