node-red / node-red/node-red-nodes
node-red-node-email, send node "ReferenceError: msg is not defined" on deploy
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
excellent write up in this thread;
Intro- the node red email node when selecting the XOauth2 setting in the interface is giving the error "ReferenceError: msg is not defined when deployed.
Which node are you reporting an issue on?
node-red-node-email, send node
What are the steps to reproduce?
set the send node to use XOuth2 authentication and deploy the flow
What happens?
on deploy the "ReferenceError: msg is not defined" is displayed in the debug panel,
What do you expect to happen?
no error on deploy.
Please tell us about your environment:
- [ 3.1.3] Node-RED version:
- [v16.20.2 ] node.js version:
- [ 8.19.4] npm version:
- [ docker container, Ubuntu 22.04.4 LTS (server) ] Platform/OS:
- [mozilla ] Browser:
docker run command
docker run -it -p 1880:1880 -p 8080:8080 -v node_red_data:/data --network="host" --name mynodered nodered/node-red
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the node-red-node-email send node and reproduce the issue by selecting XOauth2 authentication and deploying the flow in the reported environment. Trace the deploy path that produces “ReferenceError: msg is not defined”; done means deployment completes without that error and the email node remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100