Add a line mentioning that it can take up to 30 minutes for a newly published module to appear in the palette
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Open docs/creating-nodes/packaging.md and find the Adding to flows.nodered.org section. Add a note explaining that the catalog may take up to 30 minutes to regenerate before a newly published module appears in palette search. Done means the waiting period is clearly documented in that section.
Written by the indexing model from the issue text.
Description
After adding 2 custom nodes to flows.nodered.org, I went to the node-red palette but my nodes didn't appear there. I asked in the node-red slack and it seems that the catalog regenerates every 30 minutes. I'm guessing I am not the only person that was confused by this, it would be nice to add a line to the packaging.md#adding-to-flowsnoderedorg section mentioning that you may have to wait up to 30 minutes for it to appear in the search.
- Dominant language
- JavaScript
- Stars
- 118
- Forks
- 161
- Avg merge
- 8h 18m
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
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.
More from node-red/node-red.github.io
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
node-red/node-red.github.io#327 ·
-
docs/getting-started/local.md: npm command line is now deprecated, use --location=global not -g Open
Difficulty 1/5 Under an hour Newbie friendliness 62/100
node-red/node-red.github.io#280 · 1 comment ·
-
node-red/node-red.github.io#416 · 1 reaction · 1 assignee ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 50/100
node-red/node-red.github.io#384 ·
-
node-red/node-red.github.io#382 · 1 comment · 1 assignee ·
All issues in node-red/node-red.github.io
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100