Skip to content
This repository has been archived by the owner on May 22, 2020. It is now read-only.

Commit

Permalink
Update README
Browse files Browse the repository at this point in the history
  • Loading branch information
neftaly committed Mar 10, 2015
1 parent abdaa71 commit 1a589db
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
8 changes: 4 additions & 4 deletions README.md
Expand Up @@ -27,7 +27,7 @@ var element = `<link
rel='stylesheet'>`;
```

For improved preformance, use client-side caching:
For improved performance, use client-side caching:
```js
var styleSri = subresource("../public/style.css");
var element = `<link
Expand All @@ -45,12 +45,12 @@ Cache-Control: public, max-age=31536000

## Preload
Subresource operates at run-time, and caches lookups internally.
There is, however, a (very minor) one-time blocking delay whenever a new resource is encountered.
There is, however, a one-time blocking delay whenever a new resource is encountered.

Pre-loading moves this delay from the event loop to init.

**Note:** Pre-loading (or the planned async mode) is almost always unnecessary.
Use only if you are hashing hundreds of files; for thousands, try a build-time tool such as [grunt-sri](https://github.com/neftaly/grunt-sri).
**Note:** Pre-loading (or the planned async mode) is generally unnecessary.
Also consider a build-time tool such as [grunt-sri](https://github.com/neftaly/grunt-sri).

```js
var subresource = require("subresource"),
Expand Down
2 changes: 1 addition & 1 deletion package.json
@@ -1,6 +1,6 @@
{
"name": "subresource",
"version": "0.0.2",
"version": "0.0.3",
"description": "Client-side caching & SRI generation for Node",
"author": {
"name": "Neftaly Hernandez",
Expand Down

0 comments on commit 1a589db

Please sign in to comment.