From 4d1b54560d7bc90addcbe85edb91ed8e99f72d31 Mon Sep 17 00:00:00 2001 From: Joshua Bell Date: Sun, 21 Jan 2018 08:29:41 -0800 Subject: [PATCH] Throw shade on package managers --- README.md | 36 +++++++++++++++--------------------- 1 file changed, 15 insertions(+), 21 deletions(-) diff --git a/README.md b/README.md index b2781aa..b9af0e3 100644 --- a/README.md +++ b/README.md @@ -16,36 +16,30 @@ Basic examples and tests are included. ### Install ### -There are a few ways you can get the `text-encoding` library. - -#### Node #### - -`text-encoding` is on `npm`. Simply run: - -```js -npm install text-encoding -``` - -Or add it to your `package.json` dependencies. - -#### Bower #### - -`text-encoding` is on `bower` as well. Install with bower like so: - -```js -bower install text-encoding -``` - -Or add it to your `bower.json` dependencies. +There are a few ways you can get and use the `text-encoding` library. ### HTML Page Usage ### +Clone the repo and include the files directly: + ```html ``` +This is the only use case the developer cares about. If you want those +fancy module and/or package manager things that are popular these days +you should probably use a different library. + +#### Package Managers #### + +The package is published to **npm** and **bower** as `text-encoding`. +Use through these is not really supported, since they aren't used by +the developer of the library. Using `require()` in interesting ways +probably breaks. Patches welcome, as long as they don't break the +basic use of the files via `