-
Notifications
You must be signed in to change notification settings - Fork 5
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
Project improvements #20
Conversation
license
Outdated
@@ -0,0 +1,7 @@ | |||
ISC License |
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.
Should be the MIT license
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 thought so too, but previously it was "ISC" in package.json, so maybe there was a reason for 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.
Changed.
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.
💥
Currently this PR is blocked by #18, which also modifies the readme. I want to change the format little bit of API docs, so it would collide. |
4c2d539
to
3996fdd
Compare
package.json
Outdated
"repository": "segmentio/jsonrpc2", | ||
"author": { | ||
"name": "Segment", | ||
"email": "tools+npm@segment.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.
probably want friends@ for this
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.
Done.
3996fdd
to
a708c25
Compare
a708c25
to
3ca825b
Compare
I updated the readme to have a new format for API docs. I had to force push, so that the commit history is clean and we can later revert any of those changes without having to revert the whole PR. |
This PR is very similar to the one in analytics-node.
1. Add editorconfig
Ensures that all contributors write code with the same formatting according to the
standard
linter. Requireseditorconfig
plugin to be installed in the user's editor, but experience shows most of them have it.2. Remove yarn.lock and disable npm package locks (
package-lock.json
)Those are ignored by both Yarn and npm anyway, so there's no reason to include them into repository. Package locks make sense in apps, not libraries. See sindresorhus/ama#479 (comment) for a more detailed explanation.
3. Improve package.json
This change reorganizes fields in package.json to the "right" order and adds many useful things. Foe example, I added a
files
field (https://docs.npmjs.com/files/package.json#files) to include onlyindex.js
in npm package.4. Add license
Previously there was no license specified, except in package.json. I pasted license to
license
file (not.md
, since it's not markdown, but plain text), which brings useful things to our repository, such as:and
5. Remove caching of dependencies on CI
It's always preferable for CI builds to be fresh, without any previous state. Sometimes this helps to catch some nasty bugs related to dependencies.
6. Test on multiple Node.js versions on CI
This one is pretty explanatory, previously tests ran only for Node.js v4.x.x.
7. Remove continuous deployment
After talking with @stevenmiller888, we agreed that np should be used for publishing new releases.
8. Use npm scripts instead of Makefile
Makefiles are great, but in this case the whole Makefile can be replaced with a one line in package.json.
9. Remove unused dependencies
Bluebird wasn't used but was still specified as a dependency. Bye! Same for istanbul.
WIP - 10. Improve readme
Just prettify all the things.