Skip to content

Commit 3ef4779

Browse files
committed
Update naming guideline links
1 parent f30d2d1 commit 3ef4779

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

_posts/2022-01-31-introducing-scorecard.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ on the i link on the right hand side.
3636
### Changing our recommended naming convention
3737

3838
As part of the work to improve the overall quality of the Flow Libary, we're making
39-
a change to our naming guidelines for node modules.
39+
a change to our [naming guidelines for node modules](/docs/creating-nodes/packaging#naming).
4040

4141
Previously, we asked that if a module's name started with `node-red-`, that it
4242
use `node-red-contrib-` to distinguish it from modules maintained by the core project.

docs/creating-nodes/packaging.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ them easy to install along with any dependencies they may have.
1010

1111
### Naming
1212

13-
**We [updated our naming requirements](/blog/2022/01/31/introducing-scorecard) on 31st January 2022. The following applies to newly creating modules after that date.**
13+
**We [updated our naming requirements](/blog/2022/01/31/introducing-scorecard) on 31st January 2022. The following applies to modules first published after that date.**
1414

1515
Packages should use a [scoped name](https://docs.npmjs.com/cli/v8/using-npm/scope) - such as `@myScope/node-red-sample`. That can be under a user scope or an organisation scope.
1616

0 commit comments

Comments
 (0)