-
Notifications
You must be signed in to change notification settings - Fork 0
/
package.json
66 lines (66 loc) · 2.89 KB
/
package.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
{
"_args": [
[
"has-unicode@2.0.1",
"/Users/eshanker/Code/fsevents"
]
],
"_from": "has-unicode@2.0.1",
"_id": "has-unicode@2.0.1",
"_inBundle": false,
"_integrity": "sha1-4Ob+aijPUROIVeCG0Wkedx3iqLk=",
"_location": "/fsevents/has-unicode",
"_phantomChildren": {},
"_requested": {
"type": "version",
"registry": true,
"raw": "has-unicode@2.0.1",
"name": "has-unicode",
"escapedName": "has-unicode",
"rawSpec": "2.0.1",
"saveSpec": null,
"fetchSpec": "2.0.1"
},
"_requiredBy": [
"/fsevents/gauge"
],
"_resolved": "https://registry.npmjs.org/has-unicode/-/has-unicode-2.0.1.tgz",
"_shrinkwrap": null,
"_spec": "2.0.1",
"_where": "/Users/eshanker/Code/fsevents",
"author": {
"name": "Rebecca Turner",
"email": "me@re-becca.org"
},
"bugs": {
"url": "https://github.com/iarna/has-unicode/issues"
},
"dependencies": {},
"description": "Try to guess if your terminal supports unicode",
"devDependencies": {
"require-inject": "^1.3.0",
"tap": "^2.3.1"
},
"files": [
"index.js"
],
"homepage": "https://github.com/iarna/has-unicode",
"keywords": [
"unicode",
"terminal"
],
"license": "ISC",
"main": "index.js",
"name": "has-unicode",
"optionalDependencies": {},
"readme": "has-unicode\n===========\n\nTry to guess if your terminal supports unicode\n\n```javascript\nvar hasUnicode = require(\"has-unicode\")\n\nif (hasUnicode()) {\n // the terminal probably has unicode support\n}\n```\n```javascript\nvar hasUnicode = require(\"has-unicode\").tryHarder\nhasUnicode(function(unicodeSupported) {\n if (unicodeSupported) {\n // the terminal probably has unicode support\n }\n})\n```\n\n## Detecting Unicode\n\nWhat we actually detect is UTF-8 support, as that's what Node itself supports.\nIf you have a UTF-16 locale then you won't be detected as unicode capable.\n\n### Windows\n\nSince at least Windows 7, `cmd` and `powershell` have been unicode capable,\nbut unfortunately even then it's not guaranteed. In many localizations it\nstill uses legacy code pages and there's no facility short of running\nprograms or linking C++ that will let us detect this. As such, we\nreport any Windows installation as NOT unicode capable, and recommend\nthat you encourage your users to override this via config.\n\n### Unix Like Operating Systems\n\nWe look at the environment variables `LC_ALL`, `LC_CTYPE`, and `LANG` in\nthat order. For `LC_ALL` and `LANG`, it looks for `.UTF-8` in the value. \nFor `LC_CTYPE` it looks to see if the value is `UTF-8`. This is sufficient\nfor most POSIX systems. While locale data can be put in `/etc/locale.conf`\nas well, AFAIK it's always copied into the environment.\n\n",
"readmeFilename": "README.md",
"repository": {
"type": "git",
"url": "git+https://github.com/iarna/has-unicode.git"
},
"scripts": {
"test": "tap test/*.js"
},
"version": "2.0.1"
}