mattdesl / mattdesl/browserify-example
minor project updates required to keep it working
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 44
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Hi, nice example project.
To keep it running, you have to update a few details:
**package.json**
Update the versions and remove `warnings=false` from the list of uglify params.
This worked for me:
```
...
"dependencies": {
"tone": "^14.7.58"
},
"devDependencies": {
"browserify": "^17.0.0",
"budo": "^11.6.4",
"uglify-js": "^3.12.1"
},
"scripts": {
"start": "budo index.js:bundle.js --live",
"build": "browserify index.js | uglifyjs -m -c > bundle.js"
},
...
```
**index.js**
To create an instance of `Synth`
`var synth = new Tone.SimpleSynth().toMaster();`
has to be changed to
`const synth = new Tone.Synth().toDestination();`
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 with package.json and index.js, then run the listed npm start or npm run build commands to check the example. Compare the dependency versions, uglify parameters, and Tone.Synth construction with the requested updates. Done means the project installs and the build and running example work without the outdated settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100