Commit 6287118

Browse files
SmartManojSmartManoj
authored
doc: updated README.md to copy easily (#2281)
PR-URL: #2281 Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
1 parent 15a5c7d commit 6287118

1 file changed

Lines changed: 10 additions & 10 deletions

File tree

‎README.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ etc.), regardless of what version of Node.js is actually installed on your syste
2323
You can install `node-gyp` using `npm`:
2424

2525
```bash
26-
$ npm install -g node-gyp
26+
npm install -g node-gyp
2727
```
2828

2929
Depending on your operating system, you will need to install:
@@ -71,15 +71,15 @@ version `node-gyp` should use in one of the following ways:
7171
1. by setting the `--python` command-line option, e.g.:
7272

7373
```bash
74-
$ node-gyp <command> --python /path/to/executable/python
74+
node-gyp <command> --python /path/to/executable/python
7575
```
7676

7777
2. If `node-gyp` is called by way of `npm`, *and* you have multiple versions of
7878
Python installed, then you can set `npm`'s 'python' config key to the appropriate
7979
value:
8080

8181
```bash
82-
$ npm config set python /path/to/executable/python
82+
npm config set python /path/to/executable/python
8383
```
8484

8585
3. If the `PYTHON` environment variable is set to the path of a Python executable,
@@ -95,20 +95,20 @@ searching will be done.
9595
To compile your native addon, first go to its root directory:
9696

9797
```bash
98-
$ cd my_node_addon
98+
cd my_node_addon
9999
```
100100

101101
The next step is to generate the appropriate project build files for the current
102102
platform. Use `configure` for that:
103103

104104
```bash
105-
$ node-gyp configure
105+
node-gyp configure
106106
```
107107

108108
Auto-detection fails for Visual C++ Build Tools 2015, so `--msvs_version=2015`
109109
needs to be added (not needed when run by npm as configured above):
110110
```bash
111-
$ node-gyp configure --msvs_version=2015
111+
node-gyp configure --msvs_version=2015
112112
```
113113

114114
__Note__: The `configure` step looks for a `binding.gyp` file in the current
@@ -118,7 +118,7 @@ Now you will have either a `Makefile` (on Unix platforms) or a `vcxproj` file
118118
(on Windows) in the `build/` directory. Next, invoke the `build` command:
119119

120120
```bash
121-
$ node-gyp build
121+
node-gyp build
122122
```
123123

124124
Now you have your compiled `.node` bindings file! The compiled bindings end up
@@ -214,13 +214,13 @@ For example, to set `devdir` equal to `/tmp/.gyp`, you would:
214214
Run this on Unix:
215215

216216
```bash
217-
$ export npm_config_devdir=/tmp/.gyp
217+
export npm_config_devdir=/tmp/.gyp
218218
```
219219

220220
Or this on Windows:
221221

222222
```console
223-
> set npm_config_devdir=c:\temp\.gyp
223+
set npm_config_devdir=c:\temp\.gyp
224224
```
225225

226226
### `npm` configuration
@@ -230,7 +230,7 @@ Use the form `OPTION_NAME` for any of the command options listed above.
230230
For example, to set `devdir` equal to `/tmp/.gyp`, you would run:
231231

232232
```bash
233-
$ npm config set [--global] devdir /tmp/.gyp
233+
npm config set [--global] devdir /tmp/.gyp
234234
```
235235

236236
**Note:** Configuration set via `npm` will only be used when `node-gyp`

0 commit comments

Comments
 (0)
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Commit 6287118
Browse files
SmartManojSmartManoj
authored
doc: updated README.md to copy easily (#2281)
PR-URL: #2281
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
1 parent 15a5c7d commit 6287118
1 file changed
Lines changed: 10 additions & 10 deletions
File tree
‎README.md‎
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ etc.), regardless of what version of Node.js is actually installed on your syste
2323
You can install `node-gyp` using `npm`:
2424

2525
```bash
26-
$ npm install -g node-gyp
26+
npm install -g node-gyp
2727
```
2828

2929
Depending on your operating system, you will need to install:
@@ -71,15 +71,15 @@ version `node-gyp` should use in one of the following ways:
7171
1. by setting the `--python` command-line option, e.g.:
7272

7373
```bash
74-
$ node-gyp <command> --python /path/to/executable/python
74+
node-gyp <command> --python /path/to/executable/python
7575
```
7676

7777
2. If `node-gyp` is called by way of `npm`, *and* you have multiple versions of
7878
Python installed, then you can set `npm`'s 'python' config key to the appropriate
7979
value:
8080

8181
```bash
82-
$ npm config set python /path/to/executable/python
82+
npm config set python /path/to/executable/python
8383
```
8484

8585
3. If the `PYTHON` environment variable is set to the path of a Python executable,
@@ -95,20 +95,20 @@ searching will be done.
9595
To compile your native addon, first go to its root directory:
9696

9797
```bash
98-
$ cd my_node_addon
98+
cd my_node_addon
9999
```
100100

101101
The next step is to generate the appropriate project build files for the current
102102
platform. Use `configure` for that:
103103

104104
```bash
105-
$ node-gyp configure
105+
node-gyp configure
106106
```
107107

108108
Auto-detection fails for Visual C++ Build Tools 2015, so `--msvs_version=2015`
109109
needs to be added (not needed when run by npm as configured above):
110110
```bash
111-
$ node-gyp configure --msvs_version=2015
111+
node-gyp configure --msvs_version=2015
112112
```
113113

114114
__Note__: The `configure` step looks for a `binding.gyp` file in the current
@@ -118,7 +118,7 @@ Now you will have either a `Makefile` (on Unix platforms) or a `vcxproj` file
118118
(on Windows) in the `build/` directory. Next, invoke the `build` command:
119119

120120
```bash
121-
$ node-gyp build
121+
node-gyp build
122122
```
123123

124124
Now you have your compiled `.node` bindings file! The compiled bindings end up
@@ -214,13 +214,13 @@ For example, to set `devdir` equal to `/tmp/.gyp`, you would:
214214
Run this on Unix:
215215

216216
```bash
217-
$ export npm_config_devdir=/tmp/.gyp
217+
export npm_config_devdir=/tmp/.gyp
218218
```
219219

220220
Or this on Windows:
221221

222222
```console
223-
> set npm_config_devdir=c:\temp\.gyp
223+
set npm_config_devdir=c:\temp\.gyp
224224
```
225225

226226
### `npm` configuration
@@ -230,7 +230,7 @@ Use the form `OPTION_NAME` for any of the command options listed above.
230230
For example, to set `devdir` equal to `/tmp/.gyp`, you would run:
231231

232232
```bash
233-
$ npm config set [--global] devdir /tmp/.gyp
233+
npm config set [--global] devdir /tmp/.gyp
234234
```
235235

236236
**Note:** Configuration set via `npm` will only be used when `node-gyp`
0 commit comments
Comments
 (0)

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Commit 6287118
Browse files
SmartManojSmartManoj
authored
doc: updated README.md to copy easily (#2281)
PR-URL: #2281
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
1 parent 15a5c7d commit 6287118
1 file changed
Lines changed: 10 additions & 10 deletions
File tree
‎README.md‎
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ etc.), regardless of what version of Node.js is actually installed on your syste
2323
You can install `node-gyp` using `npm`:
2424

2525
```bash
26-
$ npm install -g node-gyp
26+
npm install -g node-gyp
2727
```
2828

2929
Depending on your operating system, you will need to install:
@@ -71,15 +71,15 @@ version `node-gyp` should use in one of the following ways:
7171
1. by setting the `--python` command-line option, e.g.:
7272

7373
```bash
74-
$ node-gyp <command> --python /path/to/executable/python
74+
node-gyp <command> --python /path/to/executable/python
7575
```
7676

7777
2. If `node-gyp` is called by way of `npm`, *and* you have multiple versions of
7878
Python installed, then you can set `npm`'s 'python' config key to the appropriate
7979
value:
8080

8181
```bash
82-
$ npm config set python /path/to/executable/python
82+
npm config set python /path/to/executable/python
8383
```
8484

8585
3. If the `PYTHON` environment variable is set to the path of a Python executable,
@@ -95,20 +95,20 @@ searching will be done.
9595
To compile your native addon, first go to its root directory:
9696

9797
```bash
98-
$ cd my_node_addon
98+
cd my_node_addon
9999
```
100100

101101
The next step is to generate the appropriate project build files for the current
102102
platform. Use `configure` for that:
103103

104104
```bash
105-
$ node-gyp configure
105+
node-gyp configure
106106
```
107107

108108
Auto-detection fails for Visual C++ Build Tools 2015, so `--msvs_version=2015`
109109
needs to be added (not needed when run by npm as configured above):
110110
```bash
111-
$ node-gyp configure --msvs_version=2015
111+
node-gyp configure --msvs_version=2015
112112
```
113113

114114
__Note__: The `configure` step looks for a `binding.gyp` file in the current
@@ -118,7 +118,7 @@ Now you will have either a `Makefile` (on Unix platforms) or a `vcxproj` file
118118
(on Windows) in the `build/` directory. Next, invoke the `build` command:
119119

120120
```bash
121-
$ node-gyp build
121+
node-gyp build
122122
```
123123

124124
Now you have your compiled `.node` bindings file! The compiled bindings end up
@@ -214,13 +214,13 @@ For example, to set `devdir` equal to `/tmp/.gyp`, you would:
214214
Run this on Unix:
215215

216216
```bash
217-
$ export npm_config_devdir=/tmp/.gyp
217+
export npm_config_devdir=/tmp/.gyp
218218
```
219219

220220
Or this on Windows:
221221

222222
```console
223-
> set npm_config_devdir=c:\temp\.gyp
223+
set npm_config_devdir=c:\temp\.gyp
224224
```
225225

226226
### `npm` configuration
@@ -230,7 +230,7 @@ Use the form `OPTION_NAME` for any of the command options listed above.
230230
For example, to set `devdir` equal to `/tmp/.gyp`, you would run:
231231

232232
```bash
233-
$ npm config set [--global] devdir /tmp/.gyp
233+
npm config set [--global] devdir /tmp/.gyp
234234
```
235235

236236
**Note:** Configuration set via `npm` will only be used when `node-gyp`
0 commit comments
Comments
 (0)

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Commit 6287118
Browse files
SmartManojSmartManoj
authored
doc: updated README.md to copy easily (#2281)
PR-URL: #2281
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
1 parent 15a5c7d commit 6287118
1 file changed
Lines changed: 10 additions & 10 deletions
File tree
‎README.md‎
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ etc.), regardless of what version of Node.js is actually installed on your syste
2323
You can install `node-gyp` using `npm`:
2424

2525
```bash
26-
$ npm install -g node-gyp
26+
npm install -g node-gyp
2727
```
2828

2929
Depending on your operating system, you will need to install:
@@ -71,15 +71,15 @@ version `node-gyp` should use in one of the following ways:
7171
1. by setting the `--python` command-line option, e.g.:
7272

7373
```bash
74-
$ node-gyp <command> --python /path/to/executable/python
74+
node-gyp <command> --python /path/to/executable/python
7575
```
7676

7777
2. If `node-gyp` is called by way of `npm`, *and* you have multiple versions of
7878
Python installed, then you can set `npm`'s 'python' config key to the appropriate
7979
value:
8080

8181
```bash
82-
$ npm config set python /path/to/executable/python
82+
npm config set python /path/to/executable/python
8383
```
8484

8585
3. If the `PYTHON` environment variable is set to the path of a Python executable,
@@ -95,20 +95,20 @@ searching will be done.
9595
To compile your native addon, first go to its root directory:
9696

9797
```bash
98-
$ cd my_node_addon
98+
cd my_node_addon
9999
```
100100

101101
The next step is to generate the appropriate project build files for the current
102102
platform. Use `configure` for that:
103103

104104
```bash
105-
$ node-gyp configure
105+
node-gyp configure
106106
```
107107

108108
Auto-detection fails for Visual C++ Build Tools 2015, so `--msvs_version=2015`
109109
needs to be added (not needed when run by npm as configured above):
110110
```bash
111-
$ node-gyp configure --msvs_version=2015
111+
node-gyp configure --msvs_version=2015
112112
```
113113

114114
__Note__: The `configure` step looks for a `binding.gyp` file in the current
@@ -118,7 +118,7 @@ Now you will have either a `Makefile` (on Unix platforms) or a `vcxproj` file
118118
(on Windows) in the `build/` directory. Next, invoke the `build` command:
119119

120120
```bash
121-
$ node-gyp build
121+
node-gyp build
122122
```
123123

124124
Now you have your compiled `.node` bindings file! The compiled bindings end up
@@ -214,13 +214,13 @@ For example, to set `devdir` equal to `/tmp/.gyp`, you would:
214214
Run this on Unix:
215215

216216
```bash
217-
$ export npm_config_devdir=/tmp/.gyp
217+
export npm_config_devdir=/tmp/.gyp
218218
```
219219

220220
Or this on Windows:
221221

222222
```console
223-
> set npm_config_devdir=c:\temp\.gyp
223+
set npm_config_devdir=c:\temp\.gyp
224224
```
225225

226226
### `npm` configuration
@@ -230,7 +230,7 @@ Use the form `OPTION_NAME` for any of the command options listed above.
230230
For example, to set `devdir` equal to `/tmp/.gyp`, you would run:
231231

232232
```bash
233-
$ npm config set [--global] devdir /tmp/.gyp
233+
npm config set [--global] devdir /tmp/.gyp
234234
```
235235

236236
**Note:** Configuration set via `npm` will only be used when `node-gyp`
0 commit comments
Comments
 (0)

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Commit 6287118
Browse files
SmartManojSmartManoj
authored
doc: updated README.md to copy easily (#2281)
PR-URL: #2281
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
1 parent 15a5c7d commit 6287118
1 file changed
Lines changed: 10 additions & 10 deletions
File tree
‎README.md‎
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ etc.), regardless of what version of Node.js is actually installed on your syste
2323
You can install `node-gyp` using `npm`:
2424

2525
```bash
26-
$ npm install -g node-gyp
26+
npm install -g node-gyp
2727
```
2828

2929
Depending on your operating system, you will need to install:
@@ -71,15 +71,15 @@ version `node-gyp` should use in one of the following ways:
7171
1. by setting the `--python` command-line option, e.g.:
7272

7373
```bash
74-
$ node-gyp <command> --python /path/to/executable/python
74+
node-gyp <command> --python /path/to/executable/python
7575
```
7676

7777
2. If `node-gyp` is called by way of `npm`, *and* you have multiple versions of
7878
Python installed, then you can set `npm`'s 'python' config key to the appropriate
7979
value:
8080

8181
```bash
82-
$ npm config set python /path/to/executable/python
82+
npm config set python /path/to/executable/python
8383
```
8484

8585
3. If the `PYTHON` environment variable is set to the path of a Python executable,
@@ -95,20 +95,20 @@ searching will be done.
9595
To compile your native addon, first go to its root directory:
9696

9797
```bash
98-
$ cd my_node_addon
98+
cd my_node_addon
9999
```
100100

101101
The next step is to generate the appropriate project build files for the current
102102
platform. Use `configure` for that:
103103

104104
```bash
105-
$ node-gyp configure
105+
node-gyp configure
106106
```
107107

108108
Auto-detection fails for Visual C++ Build Tools 2015, so `--msvs_version=2015`
109109
needs to be added (not needed when run by npm as configured above):
110110
```bash
111-
$ node-gyp configure --msvs_version=2015
111+
node-gyp configure --msvs_version=2015
112112
```
113113

114114
__Note__: The `configure` step looks for a `binding.gyp` file in the current
@@ -118,7 +118,7 @@ Now you will have either a `Makefile` (on Unix platforms) or a `vcxproj` file
118118
(on Windows) in the `build/` directory. Next, invoke the `build` command:
119119

120120
```bash
121-
$ node-gyp build
121+
node-gyp build
122122
```
123123

124124
Now you have your compiled `.node` bindings file! The compiled bindings end up
@@ -214,13 +214,13 @@ For example, to set `devdir` equal to `/tmp/.gyp`, you would:
214214
Run this on Unix:
215215

216216
```bash
217-
$ export npm_config_devdir=/tmp/.gyp
217+
export npm_config_devdir=/tmp/.gyp
218218
```
219219

220220
Or this on Windows:
221221

222222
```console
223-
> set npm_config_devdir=c:\temp\.gyp
223+
set npm_config_devdir=c:\temp\.gyp
224224
```
225225

226226
### `npm` configuration
@@ -230,7 +230,7 @@ Use the form `OPTION_NAME` for any of the command options listed above.
230230
For example, to set `devdir` equal to `/tmp/.gyp`, you would run:
231231

232232
```bash
233-
$ npm config set [--global] devdir /tmp/.gyp
233+
npm config set [--global] devdir /tmp/.gyp
234234
```
235235

236236
**Note:** Configuration set via `npm` will only be used when `node-gyp`
0 commit comments
Comments
 (0)

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Commit 6287118
Browse files
SmartManojSmartManoj
authored
doc: updated README.md to copy easily (#2281)
PR-URL: #2281
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
1 parent 15a5c7d commit 6287118
1 file changed
Lines changed: 10 additions & 10 deletions
File tree
‎README.md‎
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ etc.), regardless of what version of Node.js is actually installed on your syste
2323
You can install `node-gyp` using `npm`:
2424

2525
```bash
26-
$ npm install -g node-gyp
26+
npm install -g node-gyp
2727
```
2828

2929
Depending on your operating system, you will need to install:
@@ -71,15 +71,15 @@ version `node-gyp` should use in one of the following ways:
7171
1. by setting the `--python` command-line option, e.g.:
7272

7373
```bash
74-
$ node-gyp <command> --python /path/to/executable/python
74+
node-gyp <command> --python /path/to/executable/python
7575
```
7676

7777
2. If `node-gyp` is called by way of `npm`, *and* you have multiple versions of
7878
Python installed, then you can set `npm`'s 'python' config key to the appropriate
7979
value:
8080

8181
```bash
82-
$ npm config set python /path/to/executable/python
82+
npm config set python /path/to/executable/python
8383
```
8484

8585
3. If the `PYTHON` environment variable is set to the path of a Python executable,
@@ -95,20 +95,20 @@ searching will be done.
9595
To compile your native addon, first go to its root directory:
9696

9797
```bash
98-
$ cd my_node_addon
98+
cd my_node_addon
9999
```
100100

101101
The next step is to generate the appropriate project build files for the current
102102
platform. Use `configure` for that:
103103

104104
```bash
105-
$ node-gyp configure
105+
node-gyp configure
106106
```
107107

108108
Auto-detection fails for Visual C++ Build Tools 2015, so `--msvs_version=2015`
109109
needs to be added (not needed when run by npm as configured above):
110110
```bash
111-
$ node-gyp configure --msvs_version=2015
111+
node-gyp configure --msvs_version=2015
112112
```
113113

114114
__Note__: The `configure` step looks for a `binding.gyp` file in the current
@@ -118,7 +118,7 @@ Now you will have either a `Makefile` (on Unix platforms) or a `vcxproj` file
118118
(on Windows) in the `build/` directory. Next, invoke the `build` command:
119119

120120
```bash
121-
$ node-gyp build
121+
node-gyp build
122122
```
123123

124124
Now you have your compiled `.node` bindings file! The compiled bindings end up
@@ -214,13 +214,13 @@ For example, to set `devdir` equal to `/tmp/.gyp`, you would:
214214
Run this on Unix:
215215

216216
```bash
217-
$ export npm_config_devdir=/tmp/.gyp
217+
export npm_config_devdir=/tmp/.gyp
218218
```
219219

220220
Or this on Windows:
221221

222222
```console
223-
> set npm_config_devdir=c:\temp\.gyp
223+
set npm_config_devdir=c:\temp\.gyp
224224
```
225225

226226
### `npm` configuration
@@ -230,7 +230,7 @@ Use the form `OPTION_NAME` for any of the command options listed above.
230230
For example, to set `devdir` equal to `/tmp/.gyp`, you would run:
231231

232232
```bash
233-
$ npm config set [--global] devdir /tmp/.gyp
233+
npm config set [--global] devdir /tmp/.gyp
234234
```
235235

236236
**Note:** Configuration set via `npm` will only be used when `node-gyp`
0 commit comments
Comments
 (0)

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Commit 6287118
Browse files
SmartManojSmartManoj
authored
doc: updated README.md to copy easily (#2281)
PR-URL: #2281
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
1 parent 15a5c7d commit 6287118
1 file changed
Lines changed: 10 additions & 10 deletions
File tree
‎README.md‎
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ etc.), regardless of what version of Node.js is actually installed on your syste
2323
You can install `node-gyp` using `npm`:
2424

2525
```bash
26-
$ npm install -g node-gyp
26+
npm install -g node-gyp
2727
```
2828

2929
Depending on your operating system, you will need to install:
@@ -71,15 +71,15 @@ version `node-gyp` should use in one of the following ways:
7171
1. by setting the `--python` command-line option, e.g.:
7272

7373
```bash
74-
$ node-gyp <command> --python /path/to/executable/python
74+
node-gyp <command> --python /path/to/executable/python
7575
```
7676

7777
2. If `node-gyp` is called by way of `npm`, *and* you have multiple versions of
7878
Python installed, then you can set `npm`'s 'python' config key to the appropriate
7979
value:
8080

8181
```bash
82-
$ npm config set python /path/to/executable/python
82+
npm config set python /path/to/executable/python
8383
```
8484

8585
3. If the `PYTHON` environment variable is set to the path of a Python executable,
@@ -95,20 +95,20 @@ searching will be done.
9595
To compile your native addon, first go to its root directory:
9696

9797
```bash
98-
$ cd my_node_addon
98+
cd my_node_addon
9999
```
100100

101101
The next step is to generate the appropriate project build files for the current
102102
platform. Use `configure` for that:
103103

104104
```bash
105-
$ node-gyp configure
105+
node-gyp configure
106106
```
107107

108108
Auto-detection fails for Visual C++ Build Tools 2015, so `--msvs_version=2015`
109109
needs to be added (not needed when run by npm as configured above):
110110
```bash
111-
$ node-gyp configure --msvs_version=2015
111+
node-gyp configure --msvs_version=2015
112112
```
113113

114114
__Note__: The `configure` step looks for a `binding.gyp` file in the current
@@ -118,7 +118,7 @@ Now you will have either a `Makefile` (on Unix platforms) or a `vcxproj` file
118118
(on Windows) in the `build/` directory. Next, invoke the `build` command:
119119

120120
```bash
121-
$ node-gyp build
121+
node-gyp build
122122
```
123123

124124
Now you have your compiled `.node` bindings file! The compiled bindings end up
@@ -214,13 +214,13 @@ For example, to set `devdir` equal to `/tmp/.gyp`, you would:
214214
Run this on Unix:
215215

216216
```bash
217-
$ export npm_config_devdir=/tmp/.gyp
217+
export npm_config_devdir=/tmp/.gyp
218218
```
219219

220220
Or this on Windows:
221221

222222
```console
223-
> set npm_config_devdir=c:\temp\.gyp
223+
set npm_config_devdir=c:\temp\.gyp
224224
```
225225

226226
### `npm` configuration
@@ -230,7 +230,7 @@ Use the form `OPTION_NAME` for any of the command options listed above.
230230
For example, to set `devdir` equal to `/tmp/.gyp`, you would run:
231231

232232
```bash
233-
$ npm config set [--global] devdir /tmp/.gyp
233+
npm config set [--global] devdir /tmp/.gyp
234234
```
235235

236236
**Note:** Configuration set via `npm` will only be used when `node-gyp`
0 commit comments
Comments
 (0)

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Commit 6287118
Browse files
SmartManojSmartManoj
authored
doc: updated README.md to copy easily (#2281)
PR-URL: #2281
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
1 parent 15a5c7d commit 6287118
1 file changed
Lines changed: 10 additions & 10 deletions
File tree
‎README.md‎
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ etc.), regardless of what version of Node.js is actually installed on your syste
2323
You can install `node-gyp` using `npm`:
2424

2525
```bash
26-
$ npm install -g node-gyp
26+
npm install -g node-gyp
2727
```
2828

2929
Depending on your operating system, you will need to install:
@@ -71,15 +71,15 @@ version `node-gyp` should use in one of the following ways:
7171
1. by setting the `--python` command-line option, e.g.:
7272

7373
```bash
74-
$ node-gyp <command> --python /path/to/executable/python
74+
node-gyp <command> --python /path/to/executable/python
7575
```
7676

7777
2. If `node-gyp` is called by way of `npm`, *and* you have multiple versions of
7878
Python installed, then you can set `npm`'s 'python' config key to the appropriate
7979
value:
8080

8181
```bash
82-
$ npm config set python /path/to/executable/python
82+
npm config set python /path/to/executable/python
8383
```
8484

8585
3. If the `PYTHON` environment variable is set to the path of a Python executable,
@@ -95,20 +95,20 @@ searching will be done.
9595
To compile your native addon, first go to its root directory:
9696

9797
```bash
98-
$ cd my_node_addon
98+
cd my_node_addon
9999
```
100100

101101
The next step is to generate the appropriate project build files for the current
102102
platform. Use `configure` for that:
103103

104104
```bash
105-
$ node-gyp configure
105+
node-gyp configure
106106
```
107107

108108
Auto-detection fails for Visual C++ Build Tools 2015, so `--msvs_version=2015`
109109
needs to be added (not needed when run by npm as configured above):
110110
```bash
111-
$ node-gyp configure --msvs_version=2015
111+
node-gyp configure --msvs_version=2015
112112
```
113113

114114
__Note__: The `configure` step looks for a `binding.gyp` file in the current
@@ -118,7 +118,7 @@ Now you will have either a `Makefile` (on Unix platforms) or a `vcxproj` file
118118
(on Windows) in the `build/` directory. Next, invoke the `build` command:
119119

120120
```bash
121-
$ node-gyp build
121+
node-gyp build
122122
```
123123

124124
Now you have your compiled `.node` bindings file! The compiled bindings end up
@@ -214,13 +214,13 @@ For example, to set `devdir` equal to `/tmp/.gyp`, you would:
214214
Run this on Unix:
215215

216216
```bash
217-
$ export npm_config_devdir=/tmp/.gyp
217+
export npm_config_devdir=/tmp/.gyp
218218
```
219219

220220
Or this on Windows:
221221

222222
```console
223-
> set npm_config_devdir=c:\temp\.gyp
223+
set npm_config_devdir=c:\temp\.gyp
224224
```
225225

226226
### `npm` configuration
@@ -230,7 +230,7 @@ Use the form `OPTION_NAME` for any of the command options listed above.
230230
For example, to set `devdir` equal to `/tmp/.gyp`, you would run:
231231

232232
```bash
233-
$ npm config set [--global] devdir /tmp/.gyp
233+
npm config set [--global] devdir /tmp/.gyp
234234
```
235235

236236
**Note:** Configuration set via `npm` will only be used when `node-gyp`
0 commit comments
Comments
 (0)