jinx
14 April 2022 09:09
1
Node-RED version: 2.2.2(Maintenance Release)
Installation steps:
git clone GitHub - node-red/node-red: Low-code programming for event-driven applications
cd node-red
npm install
npm run build
npm start
Problem:
After put a "debug" node into a new blank flow, then press the "Deploy" button, whole web page is stucked in a gray view and following messages are shown in DevTools console of Chrome:
JQMIGRATE: Migrate is installed, version 3.3.0
Uncaught ReferenceError: hasUnusedConfig is not defined
at Object. (red.min.js?v=2.2.2:18:112007)
at c (vendor.js?v=2.2.2:2:28294)
at Object.fireWith [as resolveWith] (vendor.js?v=2.2.2:2:29039)
at l (vendor.js?v=2.2.2:2:79800)
at XMLHttpRequest. (vendor.js?v=2.2.2:2:82254)
Is this a bug ? Or what should I do to fix this?
Thanks a lot~~
Is there a reason you are cloning the code rather than installing a stable release from npm?
jinx
14 April 2022 09:44
3
You are right , installing Node-Red by:
npm install -g --unsafe-perm node-red
would fix this problem.
Thanks~ļ¼
PS: It still might be a tiny bug in master branch of github repo ~
Indeed - will need to look at that. Just wanted to make sure we got you running if you didn't really need to be running from git.
1 Like
@jinx - this issue is now resolved.
Hitachi encountered the same thing and raised a pull request to fix it.
node-red:master
ā node-red-hitachi:fix-unknown-config-error
opened 11:54PM - 17 Apr 22 UTC
<!--
## Before you hit that Submit button....
Please read our [contribution ā¦ guidelines](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
before submitting a pull-request.
## Types of changes
What types of changes does your code introduce?
Put an `x` in the boxes that apply
-->
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
<!--
If you want to raise a pull-request with a new feature, or a refactoring
of existing code, it **may well get rejected** if it hasn't been discussed on
the [forum](https://discourse.nodered.org) or
[slack team](https://nodered.org/slack) first.
-->
## Proposed changes
Recent changes in `hasUnusedConfig` variable declarations from `var` to `let` made the scope of the variable stricter.
As a result, the variable reference results in a reference error.
This PR try to corrects this.
## Checklist
- [x] I have read the [contribution guidelines](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
- [ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
- [x] I have run `grunt` to verify the unit tests pass
- [ ] I have added suitable unit tests to cover the new/changed functionality
2 Likes
system
Closed
2 May 2022 07:54
6
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.