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.

Sign up for GitHub

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

Jump to bottom

Fix npm capitalization #120

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix npm capitalization #120

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ Check it online here: [http://jubianchi.github.io/semver-check](http://jubianchi
> The bigger your system grows and the more packages you integrate into your software, the more likely you are to find yourself, one day, in this pit of despair.

More and more projects try to follow [Semantic Versioning](http://semver.org/) to reduce package versioning nightmare and every dependency manager implement its own semantic versioner.
Composer and NPM for example don't handle version constraints the same way. It's hard sometimes to be sure how some library version will behave against some constraint.
Composer and npm for example don't handle version constraints the same way. It's hard sometimes to be sure how some library version will behave against some constraint.

This tiny webapp checks if a given version satisfies another given constraint in the NPM world.
This tiny webapp checks if a given version satisfies another given constraint in the npm world.

## Run it!

Expand Down
4 changes: 2 additions & 2 deletions src/components/Implementations.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,12 +15,12 @@ const Implementations = props => (
<p>
Without any formal specification about constraint, dependency managers sometimes handle or express them
differently. For example, the tilde-range constraint (<code>~x.y</code>) does not work the same way in{' '}
<a href="https://www.npmjs.org/">NPM</a> and <a href="https://getcomposer.org">Composer</a>.
<a href="https://www.npmjs.org/">npm</a> and <a href="https://getcomposer.org">Composer</a>.
</p>

<ul>
<li>
See how <a href="https://www.npmjs.org/">NPM</a> handles constraints:{' '}
See how <a href="https://www.npmjs.org/">npm</a> handles constraints:{' '}
<a href="https://github.com/npm/node-semver">npm/node-semver</a>
</li>
<li>
Expand Down
2 changes: 1 addition & 1 deletion src/components/Why.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ const Why = props => (
<p>
More and more projects try to follow Semantic Versioning to reduce package versioning nightmare and
every dependency manager implements its own semantic versioner.{' '}
<a href="https://getcomposer.org/">Composer</a> and <a href="https://www.npmjs.org/">NPM</a> for example
<a href="https://getcomposer.org/">Composer</a> and <a href="https://www.npmjs.org/">npm</a> for example
don't handle version constraints the same way. It's hard sometimes to be sure how some library version
will behave against some constraint.
</p>
Expand Down