You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As more and more tools have become best-practice when authoring npm modules, from package.json to .*rc to *file.js, the root directory of projects has become a very loud place. This dot-noise pushes README content farther and farther down the main page of git repos.
What if the above could optionally be simplified to the following?
This is a simple example and that's already about a 30% vertical space savings. I started the conversation over in the npm repo, but I'm also submitting issues to the findup-sync, karma, travis-ci and zuul repos.
The text was updated successfully, but these errors were encountered:
As more and more tools have become best-practice when authoring npm modules, from
package.json
to.*rc
to*file.js
, the root directory of projects has become a very loud place. This dot-noise pushes README content farther and farther down the main page of git repos.What if the above could optionally be simplified to the following?
This is a simple example and that's already about a 30% vertical space savings. I started the conversation over in the npm repo, but I'm also submitting issues to the
findup-sync
,karma
,travis-ci
andzuul
repos.The text was updated successfully, but these errors were encountered: