The static import statement shows "Resolve error: Missing binary"
See original GitHub issuevscode-eslint is working my react application project on working directory. It, however, fails to find fibers package via vscode. I cant find a solution yet. please help me.
Here is my repository. https://github.com/midorizemi/react-sample.git
My environments:
- Windows10 64bit
- nvm v1.1.7 via scoop
- node v14.15.4
- npm v6.14.10
I installed npm packages, and open vscode, and add ESLint plugin in vscode.
When I typed “import” first line, vscode-eslint said the error.
I, however, tried to run npm run fix:lint
. I didn’t get any error like the error.
PS C:\Users\Public\react\sample-react> npm run fix:lint
> webpack-react-demo@ fix:lint C:\Users\Public\react\sample-react
> eslint --fix "./{lib,src,test}/**/*.{ts,tsx}"
This is the full infomation of the error from “PROBLEMS” form vscode.
{
"resource": "/c:/Users/Public/react/sample-react/src/main.tsx",
"owner": "eslint",
"code": {
"value": "import/extensions",
"target": {
"$mid": 1,
"external": "https://github.com/benmosher/eslint-plugin-import/blob/v2.22.1/docs/rules/extensions.md",
"path": "/benmosher/eslint-plugin-import/blob/v2.22.1/docs/rules/extensions.md",
"scheme": "https",
"authority": "github.com"
}
},
"severity": 8,
"message": "Resolve error: Missing binary. See message above.\n at Object.<anonymous> (C:\\Users\\Public\\react\\sample-react\\node_modules\\fibers\\fibers.js:23:9)\n at Module._compile (internal/modules/cjs/loader.js:1014:30)\n at Object.Module._extensions..js (internal/modules/cjs/loader.js:1051:10)\n at Module.load (internal/modules/cjs/loader.js:862:32)\n at Module._load (internal/modules/cjs/loader.js:774:14)\n at Function.Module._load (electron/js2c/asar.js:769:28)\n at Module.require (internal/modules/cjs/loader.js:899:19)\n at require (internal/modules/cjs/helpers.js:74:18)\n at Object.<anonymous> (C:\\Users\\Public\\react\\sample-react\\webpack.config.js:60:24)\n at Module._compile (internal/modules/cjs/loader.js:1014:30)",
"source": "eslint",
"startLineNumber": 1,
"startColumn": 1,
"endLineNumber": 1,
"endColumn": 1
}
Although I delete node_modules and reinstall npm packages, that doesn’t work. thank you.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Static import in Java - GeeksforGeeks
Ambiguity in static import: If two static members of the same name are imported from multiple different classes, the compiler will throw an...
Read more >jsp - Java error: Only a type can be imported. XYZ resolves to ...
In the last import I added a ";" by copying other code examples. ... Without further details, it sounds like an error in...
Read more >How to fix "illegal start of expression" error in Java? Example
The "illegal start of expression" error is a compile-time error when the compiler finds an inappropriate statement in the code. The java compiler,...
Read more >importlib — The implementation of import — Python 3.11.1 ...
One is to provide the implementation of the import statement (and thus, by extension, the __import__() function) in Python source code.
Read more >Python import: Advanced Techniques and Tips
Handle Packages Across Python Versions; Handle Missing Packages: Use an ... There's an equivalent absolute import statement in which you explicitly name the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Wild guess: can you use node as the runtime for eslint by using the setting
eslint.runtime
. Could be the the node shipped with Electron is not capable of executing / loading the binary.No it is not. The problem is that binaries are node version dependent. So if you install 12.18.3 it will work since the binaries are built against the right node API surface.