Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove ToneJS types repo dep, use library typescript branch instead #4

Merged
merged 1 commit into from
Dec 30, 2019

Conversation

panmichal
Copy link
Contributor

The specified ToneJS version points to the typescript branch.

Should solve #3

@@ -27,7 +27,6 @@
"devDependencies": {
"@types/jest": "^23.3.9",
"@types/node": "^10.12.5",
"@types/tone": "https://github.com/Tonejs/TypeScript.git",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mentioned TypeScript definitions come from TypeScript branch. I don't see you select the branch anywhere here? Can you explain?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed Tone version to 14.5.23.

Here https://www.npmjs.com/package/tone this version is tagged as "typescript" (under "512 versions" tab)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, that's how it works. Thank you for showing me this.

@styk-tv styk-tv merged commit 01559f9 into MusicAsCode:master Dec 30, 2019
@styk-tv
Copy link
Contributor

styk-tv commented Dec 30, 2019

Witam, PanMichal.

I need to add TravisCI auto builds so we're looking at the same output when verifying PR.

I merged both RP's a bit blindfolded and fighting with this now although seems a bit of a red herring fsevents/fsevents#246 Probably completely unrelated when versions match.

@panmichal
Copy link
Contributor Author

Hi Peter!
When do you get that error? I didn't do anything special: just npm install. It did compile fsevents without errors.
Then tested with npm run build, npm run start.
I'm running Node 10.15.1.

@styk-tv
Copy link
Contributor

styk-tv commented Dec 30, 2019

I'm running v13.5.0 need to check what is highest supported by fsevents. Will add tests in travis. finishing up.

@styk-tv
Copy link
Contributor

styk-tv commented Dec 30, 2019

@panmichal all PR's should now build in travis for verification, i triggered first manually, started with 4 node versions 10 11 12 13, we can drop some if we decide so. Check this out. All 4 failed.

https://travis-ci.org/MusicAsCode/set-player

@styk-tv
Copy link
Contributor

styk-tv commented Dec 30, 2019

yarn issue with optional dependencies (mac yes, linux no)
yarnpkg/yarn#6834

related to enforced fsevents version
master v0.2

switched travis to run build on mac because of above bug

@panmichal
Copy link
Contributor Author

panmichal commented Dec 30, 2019

Great with Travis!
I've updated my Node version to 13. Maybe it's not worth supporting 3 major versions back when 12.* is LTS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants