The specified node does not exist
See original GitHub issueSolhint does not seem to be working correctly when I lint from the command line. Installed via brew and linted with solhint test.sol
.
Solhint version 3.3.6 OSX Monterey Apple M1 Pro
/opt/homebrew/lib/node_modules/solhint/lib/index.js:40
throw e
^
Error: The specified node does not exist
at FileLevelConstantContext.getChild (/opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:9354:15)
at FileLevelConstantContext.getRuleContext (/opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:9417:19)
at FileLevelConstantContext.identifier (/opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:32322:17)
at ASTBuilder.visitFileLevelConstant (/opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:36176:22)
at FileLevelConstantContext.accept (/opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:32345:22)
at ASTBuilder.visit (/opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:17669:19)
at /opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:35327:59
at Array.map (<anonymous>)
at ASTBuilder.visitSourceUnit (/opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:35327:39)
at SourceUnitContext.accept (/opt/homebrew/lib/node_modules/solhint/node_modules/@solidity-parser/parser/dist/index.cjs.js:31855:22)
Node.js v17.2.0
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Error: The specified node does not exist · Issue #47 - GitHub
It's the 2nd time this error shows up (and I have no clue how I got there). After the first time, I just...
Read more >node.js npm error message - system cannot find the path ...
The system cannot find the path specified when starting Ruby and Rails command prompt ... Created by npm, please don't edit manually.
Read more >pcs constraint creation allows entering non-existing node ...
Fix: Warn if a node specified does not exist when creating a location constraint. Result: The user is informed the specified node does...
Read more >Node "<name>" is assigned to location or region, but does not ...
Node "<name>" is assigned to location or region, but does not exist in design · The assignment was made on a bus or...
Read more >Amazon EKS troubleshooting - AWS Documentation
The nodes may not be able to access the cluster using a public IP address. ... cluster if the security group IDs specified...
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 FreeTop 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
Top GitHub Comments
Thanks for the
3.3.7
release! It solves some issues but solhint still breaks onusing ... for ... global;
. This can be fixed by upgrading @solidity-parser/parser from0.14.1
to0.14.2-beta.1
.Unless
3.3.8
is released it can be worked around by enforcingsolhint
to use the newer version, they cooperate flawlessly. For yarn it can be done by enforcing resolution inpackage.json
:Well, I’m still an owner of the package in
npm
, so I just published this fix. Upgrade tosolhint@3.3.7
to use the version that has the updated parser.