michaelbromley / michaelbromley/chromata
non minified version doesn't work as minified
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 381
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
I have tried chromata.min.js and it works declaring a new object and then chromata.start, but with chromata.js it throws a error of "chromata element not defined". The HTML code I made for a try is the same.
Thanks
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 reproducing the report with the same HTML and initialization using chromata.js and chromata.min.js, including the new object and chromata.start call. Compare the two distributions to locate why only the unminified file reports "chromata element not defined". Done means the unminified build works with the reported example just like the minified build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100