You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
git clone https://github.com/Himself65/neon-issue-662.git
cd neon-issue-662
yarn
Error infos
{
"dependencies": {
"neon-cli": "^0.7.0"
}
}
[build-dependencies]
neon-build = "0.7.0"
[dependencies]
neon = { version = "0.7", default-features = false, features = ["napi-4"] }
> neon build
neon info running cargo
Compiling test-neon v0.1.0 (C:\Users\himse\Code\test-neon\native)
Finished dev [unoptimized+debuginfo] target(s) in0.48s
neon info generating native\index.node
neon ERR! ENOENT: no such file or directory, copyfile 'C:\Users\himse\Code\test-neon\native\target\x86_64-pc-windows-msvc\debug\test_neon.dll'->'C:\Users\himse\Code\test-neon\native\index.node'
Error: ENOENT: no such file or directory, copyfile 'C:\Users\himse\Code\test-neon\native\target\x86_64-pc-windows-msvc\debug\test_neon.dll'->'C:\Users\himse\Code\test-neon\native\index.node'
The text was updated successfully, but these errors were encountered:
In summary, with the N-API backend, eitherneon-build or neon-cli should be used, but not both. We are working on an RFC to replace neon new (neon-bindings/rfcs#36), but until then it requires small changes to a project to fix it after creation.
Reproduce steps:
Error infos
The text was updated successfully, but these errors were encountered: