sync-request
Advanced tools
Comparing version 1.0.0 to 1.0.1
{ | ||
"name": "sync-request", | ||
"version": "1.0.0", | ||
"version": "1.0.1", | ||
"description": "Make synchronous web requests", | ||
"keywords": [], | ||
"browser": "./browser.js", | ||
"keywords": ["request", "http", "https", "cache", "browserify", "synchronous", "sync"], | ||
"dependencies": { | ||
@@ -12,7 +13,4 @@ "concat-stream": "^1.4.6", | ||
}, | ||
"devDependencies": { | ||
"mocha": "*" | ||
}, | ||
"scripts": { | ||
"test": "mocha -R spec" | ||
"test": "node test" | ||
}, | ||
@@ -19,0 +17,0 @@ "repository": { |
@@ -41,3 +41,3 @@ # sync-request | ||
- `json` - sets `body` but to JSON representation of value and adds `Content-type: application/json`. Does not have any affect on how the response is treated. | ||
- `cache` - Can be `'memory'` or `'file'`, and enables a local cache of content. A separate process is still spawned even for cache requests. | ||
- `cache` - Can be `'memory'` or `'file'`, and enables a local cache of content. A separate process is still spawned even for cache requests. This option is only used if running in node.js | ||
@@ -75,4 +75,6 @@ **Returns:** | ||
This can also be used in a web browser via browserify because xhr has built in support for synchronous execution. Note that this is not recommended as it will be blocking. | ||
## License | ||
MIT |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
12183
0
12
176
79
4