sebatec-eu/forge
1
0
Fork 1
Code Issues Pull requests Activity

fix: remove TYPO #12

Merged
ses merged 1 commit from sib/forge:sb_deploy-hugo-to-hostsharing into main 2026-04-22 21:21:23 +00:00
Conversation 1 Commits 1 Files changed 1 +1 -1
sib commented 2026-04-22 16:28:03 +00:00
Contributor
Copy link

Cheers mate! With your help I was able to reproduce this howto successfully today! ;-)

Just a question out of my curiosity:

Setup project2s
npm ci || true
npm error code EUSAGE
npm error
npm error The `npm ci` command can only install with an existing package-lock.json or
npm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm error later to generate a package-lock.json file, then try again.
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts]
npm error [--allow-git <all|none|root>] [--no-audit] [--no-bin-links] [--no-fund]
npm error [--dry-run]
npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm error [--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error   --install-strategy
npm error     Sets the strategy for installing packages in node_modules.
npm error
npm error   --legacy-bundling
npm error     Instead of hoisting package installs in `node_modules`, install packages
npm error
npm error   --global-style
npm error     Only install direct dependencies in the top level `node_modules`,
npm error
npm error   --omit
npm error     Dependency types to omit from the installation tree on disk.
npm error
npm error   --include
npm error     Option that allows for defining which types of dependencies to install.
npm error
npm error   --strict-peer-deps
npm error     If set to `true`, and `--legacy-peer-deps` is not set, then _any_
npm error
npm error   --foreground-scripts
npm error     Run all build scripts (ie, `preinstall`, `install`, and
npm error
npm error   --ignore-scripts
npm error     If true, npm does not run scripts specified in package.json files.
npm error
npm error   --allow-git
npm error     Limits the ability for npm to fetch dependencies from git references.
npm error
npm error   --audit
npm error     When "true" submit audit reports alongside the current npm command to the
npm error
npm error   --bin-links
npm error     Tells npm to create symlinks (or `.cmd` shims on Windows) for package
npm error
npm error   --fund
npm error     When "true" displays the message at the end of each `npm install`
npm error
npm error   --dry-run
npm error     Indicates that you don't want npm to make any changes and that it should
npm error
npm error   -w|--workspace
npm error     Enable running a command in the context of the configured workspaces of the
npm error
npm error   --workspaces
npm error     Set to true to run the command in the context of **all** configured
npm error
npm error   --include-workspace-root
npm error     Include the workspace root when workspaces are enabled for a command.
npm error
npm error   --install-links
npm error     When set file: protocol dependencies will be packed and installed as
npm error
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-22T16_09_08_753Z-debug-0.log

Those error messages are logged during the Setup project step of the build task for my commit chore: trigger initial deployment to the main branch of my repo sib-ws-hugo. Do you expect those error messages? Are they on purpose?

Regards!

Cheers mate! With your help I was able to reproduce this [howto](https://forge.sebatec.eu/sebatec-eu/forge/src/branch/main/howto/deploy-hugo-to-hostsharing.md) successfully today! ;-) Just a question out of my curiosity: ``` Setup project2s npm ci || true npm error code EUSAGE npm error npm error The `npm ci` command can only install with an existing package-lock.json or npm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or npm error later to generate a package-lock.json file, then try again. npm error npm error Clean install a project npm error npm error Usage: npm error npm ci npm error npm error Options: npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling] npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]] npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]] npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] npm error [--allow-git <all|none|root>] [--no-audit] [--no-bin-links] [--no-fund] npm error [--dry-run] npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]] npm error [--workspaces] [--include-workspace-root] [--install-links] npm error npm error --install-strategy npm error Sets the strategy for installing packages in node_modules. npm error npm error --legacy-bundling npm error Instead of hoisting package installs in `node_modules`, install packages npm error npm error --global-style npm error Only install direct dependencies in the top level `node_modules`, npm error npm error --omit npm error Dependency types to omit from the installation tree on disk. npm error npm error --include npm error Option that allows for defining which types of dependencies to install. npm error npm error --strict-peer-deps npm error If set to `true`, and `--legacy-peer-deps` is not set, then _any_ npm error npm error --foreground-scripts npm error Run all build scripts (ie, `preinstall`, `install`, and npm error npm error --ignore-scripts npm error If true, npm does not run scripts specified in package.json files. npm error npm error --allow-git npm error Limits the ability for npm to fetch dependencies from git references. npm error npm error --audit npm error When "true" submit audit reports alongside the current npm command to the npm error npm error --bin-links npm error Tells npm to create symlinks (or `.cmd` shims on Windows) for package npm error npm error --fund npm error When "true" displays the message at the end of each `npm install` npm error npm error --dry-run npm error Indicates that you don't want npm to make any changes and that it should npm error npm error -w|--workspace npm error Enable running a command in the context of the configured workspaces of the npm error npm error --workspaces npm error Set to true to run the command in the context of **all** configured npm error npm error --include-workspace-root npm error Include the workspace root when workspaces are enabled for a command. npm error npm error --install-links npm error When set file: protocol dependencies will be packed and installed as npm error npm error npm error aliases: clean-install, ic, install-clean, isntall-clean npm error npm error Run "npm help ci" for more info npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-22T16_09_08_753Z-debug-0.log ``` Those error messages are logged during the `Setup project` step of the `build` task for my commit `chore: trigger initial deployment` to the `main` branch of my repo `sib-ws-hugo`. Do you expect those error messages? Are they on purpose? Regards!
ses commented 2026-04-22 17:21:00 +00:00
Owner
Copy link

It occurs when there is no package-lock.json. If neither package.json nor package-lock.json exists, that setup step does not make sense. My assumption was that those files always exist, which is obviously incorrect!

It occurs when there is no package-lock.json. If neither package.json nor package-lock.json exists, that setup step does not make sense. My assumption was that those files always exist, which is obviously incorrect!
ses merged commit a38ed0e65e into main 2026-04-22 21:21:23 +00:00
ses deleted branch sb_deploy-hugo-to-hostsharing 2026-04-22 21:21:23 +00:00
ses referenced this pull request from a commit 2026-04-22 21:21:25 +00:00
fix: remove TYPO (#12)
ses referenced this pull request from a commit 2026-04-22 21:29:22 +00:00
fix: remove TYPO (#12)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
sebatec-eu/forge!12
No description provided.