| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
s/customer/custom
Also, it should be noted that this is still an experimental feature.
Sorry, something went wrong.
There was a problem hiding this comment.
I believe it's been brought up before but given that --loader is still experimental I think it would it be better if it were --experimental-loader in much the same way other experimental stuff is prefixed with --experimental-
Sorry, something went wrong.
There was a problem hiding this comment.
@jdalton given you have to run node with --experimental-modules anyway to use this - why?
Sorry, something went wrong.
There was a problem hiding this comment.
thanks @jasnell ! fixed the typo.
Should i mention here, that it needs to be used with --experimental-modules?
Sorry, something went wrong.
There was a problem hiding this comment.
given you have to run node with --experimental-modules anyway to use this - why?
I like the consistency of the --experimental- prefix for experimental things. The prefix makes it explicit that the feature/sub-feature is experimental.
Sorry, something went wrong.
There was a problem hiding this comment.
esm.html#esm_loader_hooks?
Sorry, something went wrong.
There was a problem hiding this comment.
thanks! fixed now.
Sorry, something went wrong.
|
cc @nodejs/modules-active-members? |
Sorry, something went wrong.
|
It seems doc/node.1 and PrintHelp() in src/node.cc should also be updated? |
Sorry, something went wrong.
|
@vsemozhetbyt Added docs for node.1 and src/node.cc, though I couldn't maintain consistency in the doc strings. Is that fine? |
Sorry, something went wrong.
|
cc @nodejs/documentation for node.1 and src/node.cc changes. |
Sorry, something went wrong.
|
Linter issue: doc/api/cli.md 1:1 warning Missing newline character at end of file final-newline remark-lint |
Sorry, something went wrong.
|
@vsemozhetbyt thanks, installed markdown linter now. Will ensure i run this, before pushing any more doc updates. |
Sorry, something went wrong.
|
cc @nodejs/build-infra re CI error: not ok 2295 sequential/test-fs-watch
---
duration_ms: 0.111
severity: fail
exitcode: 1
stack: |-
internal/fs/watchers.js:170
throw error;
^
Error: ENOSPC: no space left on device, watch '/home/travis/build/nodejs/node/test/.tmp.0/watch.txt'
|
Sorry, something went wrong.
|
@nodejs/documentation Can anybody confident enough look into node.1 and node.cc changes so we could have some more LGTM? |
Sorry, something went wrong.
|
Another CI: https://ci.nodejs.org/job/node-test-pull-request/16313/ If CI is green, I will land this PR tomorrow if nobody objects. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM! 🎉
Sorry, something went wrong.
|
In last CIs, it seems we have some repetitive fails in parallel/test-cli-node-print-help in node-test-commit-linux-containered that may be relative. Can anybody look into? One more CI to be sure: https://ci.nodejs.org/job/node-test-pull-request/16332/ |
Sorry, something went wrong.
|
@vsemozhetbyt sorry, this maybe completely off topic, but why are --experimental-modules, --experimental-vm-modules, and --preserve-symlinks predicated on having i18n support? |
Sorry, something went wrong.
|
Sorry, this also puzzled me and I thought that it was because I just did not know C++ :) |
Sorry, something went wrong.
|
@jdalton : updated the doc for --loader option. Sounds good? Open to other wordings / text as well, to put the "experimental" point across. |
Sorry, something went wrong.
|
@SirR4T It's better. But --loader is also experimental. So maybe something like
|
Sorry, something went wrong.
| [debugger]: debugger.html | ||
| [emit_warning]: process.html#process_process_emitwarning_warning_type_code_ctor | ||
| [libuv threadpool documentation]: http://docs.libuv.org/en/latest/threadpool.html | ||
| [experimental ECMAScript Module]: esm.html#esm_loader_hooks |
There was a problem hiding this comment.
Nit: reference list is sorted in ASCII order, so this item needs to be placed before the [libuv threadpool documentation].
Sorry, something went wrong.
There was a problem hiding this comment.
Sure, will fix that. Any way we could add this as a rule to make lint?
Sorry, something went wrong.
There was a problem hiding this comment.
It would be helpful to have it as a rule as we are already a bit messy in some docs in these sections,
Sorry, something went wrong.
There was a problem hiding this comment.
Would updating remark-preset-lint-node to also include remark-lint-alphabetize-lists work? I expect this would cause build failures, if remark-preset-lint-node was updated before fixes for that landed in master. How would the transition be handled?
Sorry, something went wrong.
There was a problem hiding this comment.
I am not sure that remark-lint-alphabetize-lists can fix this case as reference lists are not common markdown lists. Maybe @rubys can tell if there is a ready easy solution for this?
Sorry, something went wrong.
There was a problem hiding this comment.
Remark calls those lines definitions. Looking at the source to remark-lint-alphabetize-lists
, if list where changed to definition on line 18, the code would do what you want.
Sorry, something went wrong.
|
#22271 is merged, so let's unblock and run CI: |
Sorry, something went wrong.
|
Rebuild failed job: https://ci.nodejs.org/job/node-test-commit-linux-containered/6326/ |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #21230
Checklist