-
Notifications
You must be signed in to change notification settings - Fork 3
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
Upgrade dev tools #26
Conversation
Pull Request Test Coverage Report for Build 10584903966Details
💛 - Coveralls |
package.json
Outdated
@@ -27,7 +27,8 @@ | |||
"@probe.gl/bench": "^4.0.0", | |||
"@turf/destination": "^6.0.1", | |||
"@types/tape-promise": "^4.0.1", | |||
"ocular-dev-tools": "2.0.0-alpha.34", | |||
"@vis.gl/dev-tools": "1.0.0-alpha.7", | |||
"@vis.gl/ts-plugins": "1.0.0-alpha.7", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a usability advantage to requiring apps to manage two separate imports? Or could dev-tools depend on/re-export ts-plugins directly?
@@ -64,7 +64,19 @@ | |||
"@math.gl/web-mercator/*": ["modules/web-mercator/src/*"], | |||
"@math.gl/web-mercator/test/*": ["modules/web-mercator/test/*"], | |||
"test/*": ["test/*"] | |||
} | |||
}, | |||
"plugins": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be managed with some "extend": "..." syntax so that we don't need to duplicate this everywhere?
Test new
@vis.gl/dev-tools
module