Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[node-red-node-ui-table] Node module cannot be loaded on this version. Requires: >=3.0.0 #49

Closed
kellycampbell opened this issue Oct 7, 2024 · 2 comments · Fixed by #50

Comments

@kellycampbell
Copy link
Contributor

I get this warning when trying to run the simulator as described at https://everest.github.io/nightly/general/03_quick_start_guide.html#software-in-a-loop
and the UI doesn't load properly.

[info] Node-RED version: v2.2.3
[info] Node.js  version: v14.19.3
[info] Linux 6.11.0-8-generic x64 LE
[info] Loading palette nodes
[warn] [node-red-node-ui-table] Node module cannot be loaded on this version. Requires: >=3.0.0 
[info] Dashboard version 3.6.5 started at /ui

I tried updating the Dockerfile to use the latest node-red:4.0.3 and it seems to work fine but not sure if this would cause other issues elsewhere. Pinning [email protected] also works.

kellycampbell added a commit to kellycampbell/everest-dev-environment that referenced this issue Oct 7, 2024
This fixes a new issue which node-red-node-ui-table 0.4.4 added which causes this warning and the UI no longer loads:
    
    Node module cannot be loaded on this version. Requires: >=3.0.0

Fixes EVerest#49

Signed-off-by: Kelly Campbell <[email protected]>
@andistorm
Copy link
Contributor

Thanks for your first contribution @kellycampbell!🎉
And also thanks for pointing this issue out.

The Dockerfile in everest-core will be removed with EVerest/everest-core#816, so could be your PR is deprecated after merging this one..

I could reproduce the issue and tried your fix, it works!

I would agree on staying with node-red:2.2.3 at the moment.

I think it would make sense to pin the version of all extensions to prevent such bugs in future, which would be at the moment:

RUN npm install [email protected]
RUN npm install [email protected]
RUN npm install [email protected]
RUN npm install [email protected]

Could you please udpate your PRs?

@kellycampbell
Copy link
Contributor Author

Updated the PR here. Did you still want me to update the other PR since that file will be going away soon anyway?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants