According to the docs, a // deno-lint-ignore directive should ignore a failing rule on the next line. The following is an example I ran where this fails:

~$ cat main.js
// deno-lint-ignore require-await
async function main() {
	console.log('hello world!');
}

main();
~$ npx denolint
error[require-await]: Async function 'main' has no 'await' expression.
 --> ~/main.js:2:1
  |
2 | / async function main() {
3 | | 	console.log('hello world!');
4 | | }
  | |_^
  |
  = help: Remove 'async' keyword from the function or use 'await' expression inside.

When I use node-rs to get segmentation result of Chinese '同方威视股份有限公司', the result is different with python/java jieba pkg, which are as follows:
node-rs:

python/java jieba pkg:

Could anyone tell me what's the problem (maybe it is not a problem)?

When using electron-forge or electron-builder we generally build our Windows apps for both ia32 and x64.

On the surface, the optional dependencies route seems like a good idea but it doesn't work in the above case because npm optional modules are installed for the current nodejs architecture, not for the target Electron arch.

None of the Electron tooling appears aware of binaries via optional dependencies route so it doesn't work for one of the architectures.

In yarn2, any module you attempt to require() must be declared as a dependency in your own package.json. This means when @node-rs/helper attempts to, for example, require('@swc/core-linux'), it fails, because @swc/core-linux is not a dependency of @node-rs/helper

Fortunately, I think the solution is simple. @node-rs/helper needs to accept the caller's require function as an argument. Then when trying to require modules, it will use the caller's require, which is able to resolve the caller's dependencies. This is what we want, since we want to be sure that the modules we load match the versions that the caller wants to use.

For backwards compatibility, this can be optional, but it will probably cause issues with yarn 2 until the callers are updated to pass in a require function.

Today, we distribute both glibc and musl variants but I think it might be possible to distribute a single binary using rustix.

• Crate: https://crates.io/crates/rustix
• Blog post: https://blog.sunfishcode.online/port-std-to-rustix/
• Additional comments: https://news.ycombinator.com/item?id=29794452

Thoughts?

node.js does not natively support dgram over UNIX sockets, and this makes talking to ubus (and so, systemd) more painful than it should. See https://www.pluralsight.com/tech-blog/using-systemd-notify-with-nodejs/

There are no great packages built on n-api offering this in Node land.

Would this be the right project to suggest creating bindings for sd_notify?
https://docs.rs/sd-notify/latest/sd_notify/

A hard reference to '/usr/bin/ldd' prevents me to use this library on NixOS.

Could we fetch it from the path?

hi there
my project was copied from package templage,
yarn build and yarn test works right, but when other projects require this module, give me the following
(mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e'))

reproduce steps

1. execute command yarn link @${module_name} in the addon module dir
2. execute command yarn link in the caller project dir
3. use it let {xxx} = require('@${module_name}')

能否提供一个获取词性的示例呢？
以及所有词性的清单
谢谢

Hi!

I would like to include some linting rules and exclude the dist directory.
The files field seems not supported in the config file. The combination of a config file and a path as argument seem not supported either (the path is ignored).

I tried the following config file:

{
  "files": {
    "include": ["src/"],
    "exclude": ["dist/"]
  },
  "rules": {
    "tags": ["recommended"],
    "include": [
      "camelcase"
    ]
  }
}

And the following commands:

npx denolint --config denolint.json
npx denolint --config denolint.json src/

It could be nice whether one of this (or both) could be supported.

I tried installing a package that depends on SWC, @node-rs/helpers throws the following error.

Can not find node binding files from @swc/core-linux-arm64-gnu, @swc/core-linux-arm64-musl and /origin/aio/node_modules/@swc/core/swc.linux-arm64-gnu.node, /origin/aio/node_modules/@swc/core/swc.linux-arm64-musl.node

The environment is on node:14 docker image and the host machine is M1 Mac.

# Host 
$ uname -ms
Darwin arm64

# Container
$ uname -ms
Linux aarch64

I expect darwin/arm64 is supported but Linux/aarch64 isn't. Is it right? And how can I do to solve this error?

jieba-rs can load a custom IDF dict, but @node-rs/jieba does not provide the corresponding binding.

https://github.com/messense/jieba-rs/blob/2da3243c013af8d6f3f4c6c1a474fb7215c1f4cc/src/keywords/tfidf.rs#L56

https://crates.io/crates/jsonwebtoken

您好,
請問extract可以產生 weight-value 嗎? 類似 node-jieba

ex :
//[ { word: 'CEO', weight: 11.739204307083542 },
// { word: '升职', weight: 10.8561552143 },
// { word: '加薪', weight: 10.642581114 },
// { word: '巅峰', weight: 9.49395840471 } ]

When hoist is turned off in pnpm monorepo, packages which were not listed in package.json will not be accessible to current node path.
This leads a runtime failure like "TypeError: Not compatible with your platform. Error message: Cannot find module '@node-rs/crc32-darwin'"

I'm using crc32c to create checksums that are stored in Postgres as an int. Their ints are signed, and often the result of crc32c() goes outside the bounds of a signed int (4 bytes, -2147483648 to +2147483647) because crc32c() returns an unsigned int value it seems. I can adjust with crc >>> 0 but it would be nice to document this in the API.

Even better, if the rust lib supports generating unsigned crc values then provide an option to do so.

Thanks for the fast lib!

Reproduction: https://gist.github.com/BasixKOR/6841d085a82e0d7f8811d33894adf17c

Dump:

> require('./dist/foo.bundle.js')
node /c/Users/basix/Projects/repro-node-rs[16908]: c:\ws\src\node_buffer.cc:246: Assertion `val->IsArrayBufferView()' failed.
 1: 00007FF71FE0013F v8::internal::CodeObjectRegistry::~CodeObjectRegistry+112495
 2: 00007FF71FD8F396 DSA_meth_get_flags+65526
 3: 00007FF71FD8F751 DSA_meth_get_flags+66481
 4: 00007FF71FDB0F28 node::Buffer::Data+168
 5: 00007FF71FDC004F napi_get_buffer_info+79
 6: 00007FFDB69F2CCD napi_register_module_v1+2621
 7: 00007FF71FDCE7C7 node::Stop+36391
 8: 00007FF72067C3B6 v8::internal::Builtins::code_handle+172694
 9: 00007FF72067BFA9 v8::internal::Builtins::code_handle+171657
10: 00007FF72067C26C v8::internal::Builtins::code_handle+172364
11: 00007FF72067C0D0 v8::internal::Builtins::code_handle+171952
12: 00007FF72074F4E1 v8::internal::SetupIsolateDelegate::SetupHeap+494673
13: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
14: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
15: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
16: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
17: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
18: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
19: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
20: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
21: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
22: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
23: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
24: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
25: 00007FF7206DFB9C v8::internal::SetupIsolateDelegate::SetupHeap+37644
26: 00007FF7206DF79B v8::internal::SetupIsolateDelegate::SetupHeap+36619
27: 00007FF7205C0471 v8::internal::Execution::CallWasm+1521
28: 00007FF7205BFD5F v8::internal::Execution::Call+191
29: 00007FF7206C22EA v8::Script::Run+890
30: 00007FF71FD9AE88 node::OnFatalError+44392
31: 00007FF71FD9E5A6 node::OnFatalError+58502
32: 00007FF72067C3B6 v8::internal::Builtins::code_handle+172694
33: 00007FF72067BFA9 v8::internal::Builtins::code_handle+171657
34: 00007FF72067C26C v8::internal::Builtins::code_handle+172364
35: 00007FF72067C0D0 v8::internal::Builtins::code_handle+171952
36: 00007FF72074F4E1 v8::internal::SetupIsolateDelegate::SetupHeap+494673
37: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
38: 00007FF7206E198E v8::internal::SetupIsolateDelegate::SetupHeap+45310
39: 00000273D1FB74C1

Hello 👋

First, thanks for these awesome bindings, these are awesome!

I'm having a question / feature request (it might be possible, but I don't know how): Is there a way to fail on error with the denolint CLI? I saw that it's possible with the Webpack plugin, but we would like to run denolint in our CI and see it fails if there is some errors.

Hello, When I use it in my nodejs project. After I packaged a application for windows use electron-builder. App can work normally on most machines. But this error appeared on a small number of machines. I don't know about "gnu" or "msvc". Do you know the reason for this?　

Checking the sources can take a long time. Blocking the whole JavaScript VM should be avoided. The API could be changed to support asynchronous execution and let retain the synchronous methods with the well-known Sync suffix. For example:

function lint(filepath: string, source: string, enableAllRules?: boolean): Promise<string[]>
function lintSync(filepath: string, source: string, enableAllRules?: boolean): string[]

function denolint(dirname: string, configPath: string): Promise<boolean>
function denolintSync(dirname: string, configPath: string): boolean

Would you be interested in such improvement?

• NodeJS - 12.22.1
• @node-rs/bcrypt - 1.5.0

calling verify function with malformed hash causes nodejs process to hang

POC:

const bcrypt = require('@node-rs/bcrypt');

try {
  const result = bcrypt.verifySync('test', '$2b$10$heNneCqWJ6/hd5pb.Pbgs.Jzc/qnqf3gQRNiGkr9KbS2yFdozfQ50');
  console.log(result);
} catch (e) {
  console.log(e);
}

Output:

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: InvalidTrailingBits', packages/bcrypt/src/b64.rs:181:23
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
[1]    17750 abort      node bcrypt-panic-poc.js

I have changed last character of hash from 2 to 0

服务器：Windows Server 2008R2
node版本：v12.18.3
安装报错：
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fse vents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@ 2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"} )
启动报错：
(node:4904) UnhandledPromiseRejectionWarning: Error: The specified module could not be found. \\?\F:\diffTest_server\node_modules\@node-rs\jieba\jieba.win32.node at Object.Module._extensions..node (internal/modules/cjs/loader.js:1187:18) at Module.load (internal/modules/cjs/loader.js:985:32) at Function.Module._load (internal/modules/cjs/loader.js:878:14) at Module.require (internal/modules/cjs/loader.js:1025:19) at require (internal/modules/cjs/helpers.js:72:18) at loadBinding (F:\diffTest_server\node_modules\@node-rs\helper\lib\loader.j s:27:12) at Object.<anonymous> (F:\diffTest_server\node_modules\@node-rs\jieba\index. js:3:16) at Module._compile (internal/modules/cjs/loader.js:1137:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10) at Module.load (internal/modules/cjs/loader.js:985:32) (node:4904) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termina te the node process on unhandled promise rejection, use the CLI flag --unhandle
d-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejectio ns_mode). (rejection id: 2) (node:4904) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre cated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@node-rs/argon2 only has the feature to output base64-encoded strings. But node-argon2 can obtain a raw hash by specifying the raw option.

看.d.ts的参数类型是Buffer而不是引入一个像nodejieba中.utf-8的文件

Similarly to esbuild, why not building denolint as a Rust executable and call it directly on the command line? Less complexity, better performance.

The command line executable is usually used alone. If linting is integrated to webpack, rollup or other bundler, the library with the lint export will be used programmatically instead of the executable. For example, the deno_lint package could be split to denolint producing just the executable and libdenolint producing just the library with the Node.js bindings:

├── crates
│   ├── alloc
│   │   ├── Cargo.toml
│   │   └── src
│   │       └── lib.rs
│   └── shared                  # config and diagnostics moved here
│       ├── Cargo.toml
│       └── src
│           ├── config.rs
│           ├── diagnostics.rs
│           └── lib.rs
└── packages
    ├── denolint                # depends on alloc and shared
    │   ├── Cargo.toml
    │   ├── package.json
    │   └── src
    │       └── main.rs
    └── libdenolint             # depends on alloc and shared
        ├── Cargo.toml
        ├── build.rs
        ├── index.d.ts
        ├── index.js
        ├── package.json
        └── src
            └── lib.rs

Would you be interested in such change?

Symphonia is a pure Rust audio decoding and media demuxing library supporting AAC, ALAC, FLAC, MKV, MP3, MP4, OGG, Vorbis, WAV, and WebM.

https://github.com/pdeljanov/Symphonia

调用load开头的均报这个错

Both ncc and electron-forge rely on @vercel/webpack-asset-relocator-loader to locate and copy native node assets.

@vercel/webpack-asset-relocator-loader supports many conventions, works with wildcards, __dirname and has special cases for historic ways to load a native binary (ie. require('bindings')(...), nbind.init(..), etc). However, it's analysis fails to make sense of the binding loading code in @node-rs/helper because it's too complex.

To reproduce:

package.json

{
  "name": "ncc-test",
  "version": "1.0.0",
  "main": "dist/index.js",
  "license": "MIT",
  "scripts": {
    "start": "node ./dist/index.js -v",
    "build": "ncc build index.js -o dist"
  },
  "devDependencies": {
    "@vercel/ncc": "^0.27.0"
  },
  "dependencies": {
    "@node-rs/crc32": "^1.0.0"
  }
}

index.js

const crc = require("@node-rs/crc32");
const out = crc.crc32(Buffer.from([1, 2, 3, 4, 5, 6, 7, 8, 9]));
console.log("out", out);

Run

yarn && yarn build && yarn run

Result:
Can not find node binding files from @node-rs/crc32-darwin-x64 and /Users/timfish/Documents/Repositories/ncc-test/dist/crc32.darwin-x64.node

It would be great the have a wrapper for snappy (https://github.com/BurntSushi/rust-snappy)

Hi,

N00b Rust learner here. I'm trying to build the packages in main (3e555f1) using yarn build and getting the following error:

 ~/C/node-rs    yarn build                                             36.3s  Tue Jan 18 13:52:57 2022
yarn run v1.22.11
$ lerna run build --concurrency 1 --stream --no-prefix
lerna notice cli v4.0.0
lerna info versioning independent
lerna info Executing command in 7 packages: "yarn run build"
$ napi build --platform --release --pipe "prettier -w"
   Compiling cfg-if v1.0.0
   Compiling libc v0.2.112
   Compiling autocfg v1.0.1
   Compiling typenum v1.15.0
   Compiling lazy_static v1.4.0
   Compiling proc-macro2 v1.0.36
   Compiling version_check v0.9.4
   Compiling crossbeam-utils v0.8.6
error: the option `Z` is only accepted on the nightly compiler
error: the option `Z` is only accepted on the nightly compiler
error: the option `Z` is only accepted on the nightly compiler
error: the option `Z` is only accepted on the nightly compiler
error: the option `Z` is only accepted on the nightly compiler
error: the option `Z` is only accepted on the nightly compiler
error: the option `Z` is only accepted on the nightly compiler
error: the option `Z` is only accepted on the nightly compiler
error: could not compile `typenum`
warning: build failed, waiting for other jobs to finish...
error: build failed
Internal Error: Command failed: cargo build --release
    at checkExecSyncError (child_process.js:635:11)
    at Object.execSync (child_process.js:671:15)
    at BuildCommand.<anonymous> (/Users/mohsen_azimi/Code/node-rs/node_modules/@napi-rs/cli/scripts/index.js:12797:26)
    at Generator.next (<anonymous>)
    at /Users/mohsen_azimi/Code/node-rs/node_modules/@napi-rs/cli/scripts/index.js:1678:71
    at new Promise (<anonymous>)
    at __awaiter$1 (/Users/mohsen_azimi/Code/node-rs/node_modules/@napi-rs/cli/scripts/index.js:1674:12)
    at BuildCommand.execute (/Users/mohsen_azimi/Code/node-rs/node_modules/@napi-rs/cli/scripts/index.js:12721:16)
    at BuildCommand.validateAndExecute (/Users/mohsen_azimi/Code/node-rs/node_modules/@napi-rs/cli/scripts/index.js:204:37)
    at /Users/mohsen_azimi/Code/node-rs/node_modules/@napi-rs/cli/scripts/index.js:1261:53
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! yarn run build exited 1 in '@node-rs/argon2'
lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
 !  ~/C/node-rs                                                      2766ms  Tue Jan 18 13:53:02 2022

My Rust versions:

Default host: x86_64-apple-darwin
rustup home:  /Users/mohsen_azimi/.rustup

installed toolchains
--------------------

stable-x86_64-apple-darwin (default)
nightly-2021-12-05-x86_64-apple-darwin

active toolchain
----------------

nightly-2021-12-05-x86_64-apple-darwin (overridden by '/Users/mohsen_azimi/Code/node-rs/rust-toolchain')
rustc 1.59.0-nightly (efec54529 2021-12-04)

I've installed a package that has node-rs/helper@^1.2.0 as a dependency in my create-react-app project and I'm getting these warnings when running the dev server:

./node_modules/@node-rs/helper/lib/loader.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

./node_modules/@node-rs/helper/lib/loader.js 25:15-27:11
Critical dependency: the request of a dependency is an expression

./node_modules/@node-rs/helper/lib/loader.js
Critical dependency: the request of a dependency is an expression

I'm still looking into it.

I tried installing gcompat or libc6-compat:

Error relocating /usr/node_modules/@node-rs/bcrypt/bcrypt.linux.node: __register_atfork: symbol not found

Without them:

Error: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /usr/node_modules/@node-rs/bcrypt/bcrypt.linux.node)

My dockerfile:

FROM node:14-alpine

# Create app directory
RUN mkdir -p /usr
WORKDIR /usr

COPY package*.json ./
RUN apk add --no-cache gcompat \
    && npm install --production

After installing on alpine docker container, I see such an error:

Loading linux musl addon Error: Cannot find module '@node-rs/bcrypt-linux-musl'
Require stack:
- /usr/src/app/node_modules/@node-rs/helper/lib/loader.js
- /usr/src/app/node_modules/@node-rs/helper/lib/index.js
- /usr/src/app/node_modules/@node-rs/bcrypt/index.js
- /usr/src/app/node_modules/http-auth/src/auth/basic.js
- /usr/src/app/node_modules/http-auth/src/http-auth.js

Could you please help me to handle it.

node_modules/@node-rs/xxhash/index.d.ts:30:25 - error TS1183: An implementation cannot be declared in ambient contexts.

30   private constructor() {}
                           ~

I am using typescript 4.3.5 in strict mode.

https://crates.io/crates/glob

It looks like ARMv8 has CRC32C instructions available.

https://elixir.bootlin.com/linux/v4.6/source/arch/arm64/crypto/crc32-arm64.c

winserver2012 R2 无法使用，是否还缺少环境没安装，同样代码其他电脑正常。
系统

示例代码

运行失败

https://docs.rs/notify/latest/notify/

7914fd5#diff-42a695a5f1b341348435086cf64d321a61781da8de022c52f3b0f4d37ce80a28

This commit removed the compare function export from @node-rs/bcrypt which should have been a breaking change if this project follows semver, since only verify can be used now. The README also still contains a reference to it: https://github.com/napi-rs/node-rs/blob/main/packages/bcrypt/README.md?plain=1#L42

小白求助，如题

Hope you don't mind me submitting 2 separate issues at once, but I don't think this is related to #630.

It seems the denolint cli ignores the path parameter and lints everything recursively, starting at the cwd. Example where I point it at a file with a single script, and it lints a second script in the current directory anyway:

~$ tree
.
├── main.js
└── test
    └── main2.js

1 directory, 2 files
~$ npx denolint test
error[require-await]: Async function 'main' has no 'await' expression.
 -->~/test/main2.js:2:1
  |
2 | / async function main() {
3 | | 	console.log('hello world!');
4 | | }
  | |_^
  |
  = help: Remove 'async' keyword from the function or use 'await' expression inside.
error[require-await]: Async function 'main' has no 'await' expression.
 --> ~/test/main.js:2:1
  |
2 | / async function main() {
3 | | 	console.log('hello world!');
4 | | }
  | |_^
  |
  = help: Remove 'async' keyword from the function or use 'await' expression inside. 

Would it be possible to get @node-rs/jieba working as a client side library for the browser?

There are bcrypt functions exposed for generating salts (genSalt/genSaltSync), but it doesn't seem possible to pass their returned values to hash() as an alternative to the rounds parameter. I didn't see anything in the documentation or examples -- and it didn't seem possible in the source nor did there seem to be any tests that combined the functions. Did I just miss how to do it? Or is this an oversight / just not supported yet?