Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
94c282db
Commit
94c282db
authored
Mar 05, 2020
by
Robin Cussol
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos in monorepo package workflow docs
parent
3ea8f2f2
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/user/packages/workflows/monorepo.md
doc/user/packages/workflows/monorepo.md
+3
-3
No files found.
doc/user/packages/workflows/monorepo.md
View file @
94c282db
...
...
@@ -38,14 +38,14 @@ If you follow the instructions you can publish `MyProject` by running
`npm publish`
from the root directory.
Publishing
`Foo`
is almost exactly the same, you simply have to follow the steps
while in the
`Foo`
directory.
`Foo`
will need it
'
s own
`package.json`
file,
which can be added manually or using
`npm init`
. And it will need it
'
s own
while in the
`Foo`
directory.
`Foo`
will need its own
`package.json`
file,
which can be added manually or using
`npm init`
. And it will need its own
configuration settings. Since you are publishing to the same place, if you
used
`npm config set`
to set the registry for the parent project, then no
additional setup is necessary. If you used a
`.npmrc`
file, you will need an
additional
`.npmrc`
file in the
`Foo`
directory (be sure to add
`.npmrc`
files
to the
`.gitignore`
file or use environment variables in place of your access
tokens to preven them from being exposed). It can be identical to the
tokens to preven
t
them from being exposed). It can be identical to the
one you used in
`MyProject`
. You can now run
`npm publish`
from the
`Foo`
directory and you will be able to publish
`Foo`
separately from
`MyProject`
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment