Build command fails on generated theme

npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.org/string.prot.trimstart - Not found npm error 404 npm error 404 'string.custom_theme.trimstart@1.0.8' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/john/.npm/_logs/2025-06-08T06_59_03_198Z-debug-0.log

Comments & Activities

Issue created by @jemandy
Comment 4 months ago →
🇺🇸United States jldust
Comment 4 months ago →
🇺🇸United States jldust
The step before npm use is npm install, please verify that has be run.
Comment 4 months ago →
🇺🇸United States jldust
Comment 4 months ago →
🇺🇸United States pixelwhip
I've come across this bug before. This happens when `npm install` has been run inside the `prototype` theme itself. The problem is that Drupal theme rename utility is replacing all instances of the sting "prototype" which is a reserved property name in JS. Typically deleting the `node_modules` folder and re-running the script will fix it.
Merge request !199Issue 3529055: Updating starterkit ignore → (Open) created by jldust
Assigned to jldust
Status changed to Postponed: needs info about 2 months ago9:17pm 3 September 2025

Build command fails on generated theme

Problem/Motivation

Steps to reproduce

Proposed resolution

Merge Requests

!199Build command fails on generated theme
Open

Comments & Activities

Build command fails on generated theme

Problem/Motivation

Steps to reproduce

Proposed resolution

Merge Requests

!199Build command fails on generated themeOpen

Comments & Activities

!199Build command fails on generated theme
Open