-
Notifications
You must be signed in to change notification settings - Fork 0
Initialize package.json in content folder #32
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
Changes from all commits
98359a5
94d92bb
6b7adab
2be2a4e
2219503
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,9 +4,9 @@ | |
| "private": true, | ||
| "description": "Starter template for creating documentation sites with ObjectDocs", | ||
| "scripts": { | ||
| "dev": "objectdocs dev", | ||
| "build": "objectdocs build", | ||
| "start": "objectdocs start" | ||
| "dev": "cd content && npm run dev", | ||
| "build": "cd content && npm run build", | ||
| "start": "cd content && npm run start" | ||
|
Comment on lines
+7
to
+9
|
||
| }, | ||
| "devDependencies": { | ||
| "@objectdocs/cli": "workspace:*" | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The instructions here recommend running
npm run init, but the earlierscriptssnippet for a new standalone project only definesdev,build, andstartscripts and does not include aninitscript. Either thescriptsexample should add aninitscript, or this command should be updated to use the CLI directly (for example vianpx @objectdocs/cli init), otherwisenpm run initwill fail for users following these steps.