-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update deps #11
Update deps #11
Conversation
Argh. Looks like I will need to update node as part of this change |
Not sure if we also want to update the other dependencies that are out of date ( |
@@ -102,7 +102,7 @@ This repository is configured with [EditorConfig](http://editorconfig.org) rules | |||
[npm-url]: https://www.npmjs.org/package/frau-appconfig-builder | |||
[npm-image]: https://img.shields.io/npm/v/frau-appconfig-builder.svg | |||
[ci-url]: https://travis-ci.org/Brightspace/frau-appconfig-builder | |||
[ci-image]: https://img.shields.io/travis-ci/Brightspace/frau-appconfig-builder.svg |
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.
I think we want this URL: https://img.shields.io/travis/com/Brightspace/frau-appconfig-builder.svg
We try to use the badges from img.shields.io
for consistency, otherwise they are different size/font and they look terrible.
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.
Ok thanks! The existing badge was broken but the one in the link you provided works
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.
Cool yeah, I think we probably have a few that are broken due to the switch to travis.com.
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.
This looks ok to me. I'd probably try to update the other dependencies you asked about as well. It'd be good to get someone elses eyes on this since I haven't worked with appconfig in years.
TODO:
|
|
||
argv = argv.usage('Usage: frau-appconfig-builder [--appfile|-f] [--dist|-d] [--loader|l] [--showloading|-s]') | ||
argv = argv.usage('Usage: frau-appconfig-builder [--appfile|-f] [--dist|-d] [--loader|-l] [--showloading|-s]') |
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.
nice!
.travis.yml
Outdated
@@ -1,6 +1,6 @@ | |||
language: node_js | |||
node_js: | |||
- '0.12' | |||
- '6.9' |
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.
wow, really? It was on 0.12?
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.
Lol yeah. One of the dependencies used const
and travis freaked out when I tried to test it
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.
Have you searched if people were consuming this programmatically, or are they just using the cli?
Transformations done seem okay to me, though they are breaking (hence the question above). The end result is still imperfect error-handling wise, but not something that needs to be fixed here.
test/mocha.opts
Outdated
@@ -1 +1 @@ | |||
--compilers js:babel/register -R spec | |||
--require @babel/register -R spec |
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.
I don't believe babel is needed at this point.
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.
That's because recent versions of node support ES5/ES6 features natively, right?
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.
Right. I expect this was mostly in here to be able to use, say, const
in the tests.
.travis.yml
Outdated
@@ -1,6 +1,6 @@ | |||
language: node_js | |||
node_js: | |||
- '0.12' | |||
- '6.9' |
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.
Node.js 6 was EOL in April. If we're updating things, not a ton of point in including or, or at least having it as the only version.
Maybe do a list of 8, 10 and 12
Looks like they are, which is not a case I considered. Example: https://github.com/Brightspace/simplified-interface-checklist/blob/master/bin/build-appconfig.js If I still want to go ahead with this change, I guess I should bump the major version number ( |
Yeah, and ideally open a PR against the users so the company isn't sitting stale. I know that makes more work for you though. If you wanted to stay non-breaking, you'd want to put vinyl back in probably. |
@@ -1,8 +1,8 @@ | |||
import chai from 'chai'; |
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.
this wasn't you.. but anyone else notice that space in the filename?
For something that was part of inspiration I don't want to spend that much time on this :) |
Continuing what @jwong-d2l started in #10:
remove(EDIT:vinyl-fs
vinyl-fs
is back. Too many consumers of this module are still using vinyl),modernizedelete babel, and update dev dependencies. With these changes there are 0 known vulnerabilities in this package (down from 38)!Testing:
npm link
ed it to my local clone ofbdp-visualizations-fra
and ran the script. It buildsappconfig.json
correctly, in the location specified indist
. The file is always calledappconfig.json
, which I'm pretty sure was the case before.yargs
command line arguments and aliases still workpackage.json
still workschalk
still prints in the correct coloursNote: if you're running from command line,
frau-appconfig-builder
will likely fail because you haven't specified anappClass
.