Building a forked version of kepler.gl
- Dominant language
- TypeScript
- Stars
- 12k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 66
Description
Hi,
I want to make some specific changes to kepler.gl to best suit my needs. To do so, I forked this repo and linked the fork to my dependencies by running: `yarn add ssh://git@github.com:blanch0t/kepler.gl.git`. This works but basically just copies everything from the repo to the `node_modules/kepler.gl` folder.
To make it useful I added `"prepare": "yarn run build"` to the `package.json` of the fork, which makes the repo build at installation time (this is the only change I made). However, the build results in a dist folder which hierarchy is very different from the one's we get by installing the npm package, making it unusable.
Please tell me what am I doing wrong and how to actually use a forked version of kepler.gl.
Thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with package.json and the prepare script described in the issue, then run the forked repository build and inspect the generated dist folder. Compare that output with the dist hierarchy from the published npm package and trace where the packaging layouts diverge. Done means the fork can be installed with yarn and used like the npm package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100