User tests: Successful: Unsuccessful:
Pull Request resolves #47755 .
Currently, run npm ci on Windows produce some errors. This PR fixes that error. Honestly, I do not understand the script, this fix is provided completely by Copilot. I just makes this PR because I am using Windows and confirm that the fix worked.
There are some errors
No errors anymore.
Please select:
Documentation link for guide.joomla.org:
No documentation changes for guide.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | JavaScript Repository |
I have tested this item ✅ successfully on d02d361
Works fine for me on Windows 11
I have tested this item ✅ successfully on d02d361
I have tested this item ✅ successfully on d02d361
| Status | Pending | ⇒ | Ready to Commit |
RTC. Thanks
RTC. Thanks
Didn't work for me, windows 10.
I will try again and update if it works.
Didn't work for me, windows 10. I will try again and update if it works.
Can you check your node version? Should not be a Windows 10 problem, but we won't go down that rabbithole
Didn't work for me, windows 10. I will try again and update if it works.
Can you check your node version? Should not be a Windows 10 problem, but we won't go down that rabbithole
Tried again still didn't work.
Node version: 22.16.0
NPM version: 11.14.1
Didn't work for me, windows 10. I will try again and update if it works.
Can you check your node version? Should not be a Windows 10 problem, but we won't go down that rabbithole
Tried again still didn't work.
Node version: 22.16.0
NPM version: 11.14.1
Windows 10.
@CSGoat0 In my case, I have node v24.13.0. npm 11.7.0 . So the reason could be because your node version is old
I have tried again with Node version v24.15.0 and unfortunately it didn't work.
I have also tried on a fresh Joomla 6.2 branch, and it didn't work.
Maybe if someone else have Windows 10, they can confirm.
But making it works for 11 is good though.
When testing please make sure that you are testing without anything in the media folder
I have tested this item 🔴 unsuccessfully on d02d361
I have tested this item 🔴 unsuccessfully on d02d361
Failed Task [system::js]
Trace: Error: Processing failed for "D:\repos\j61\media_source\system\js\fields\joomla-field-color-slider.es6.js".
at file:///D:/repos/j61/build/build-modules-js/javascript/js-handle.mjs:157:11
at async Promise.all (index 23) {
[cause]: Error: ENOENT: no such file or directory, mkdir 'D:\repos\j61\media\system\js\fields'
at async mkdir (node:internal/fs/promises:859:10)
at async writeOutputFile (file:///D:/repos/j61/node_modules/rollup/dist/es/shared/node-entry.js:23616:5)
at async Queue.work (file:///D:/repos/j61/node_modules/rollup/dist/es/shared/node-entry.js:22681:32) {
errno: -4058,
code: 'ENOENT',
syscall: 'mkdir',
path: 'D:\\repos\\j61\\media\\system\\js\\fields'
}
}
at file:///D:/repos/j61/build/build-modules-js/builder/builder-factory.mjs:74:21
PS D:\repos\j61> node -v
v24.15.0
PS D:\repos\j61> npm -v
11.14.1
windows 11
I have tested this item 🔴 unsuccessfully on d02d361npm ci works now👍(tested with win11; npm 11.14.1; node 22.22.2)
but uri of codemirror files in joomla.asset.json is wrong -> codemirror not working

I have tested this item 🔴 unsuccessfully on d02d361npm ci works now👍(tested with win11; npm 11.14.1; node 22.22.2)
but uri of codemirror files in joomla.asset.json is wrong -> codemirror not working

| Status | Ready to Commit | ⇒ | Pending |
| Labels |
Added:
bug
PR-6.2-dev
|
||
Back to pending due to new, unsuccessful human tests.
Back to pending due to new, unsuccessful human tests.
@heelc29 would this resolve the issue? I'm opening a PR against @joomdonation branch, but maybe you could test it out beforehand @heelc29 @CSGoat0 ? Unfortunately, I can't.
media_source/plg_editors_codemirror/builder.mjs
uri: modulePath.replace('.js', '.min.js').replace(/\\/g, '/'),
@heelc29 would this resolve the issue? I'm opening a PR against @joomdonation branch, but maybe you could test it out beforehand @heelc29 @CSGoat0 ? Unfortunately, I can't.
media_source/plg_editors_codemirror/builder.mjs
uri: modulePath.replace('.js', '.min.js').replace(/\\/g, '/'),@heelc29 would this resolve the issue? I'm opened a PR (joomdonation#6) against @joomdonation branch, but maybe you could test it out beforehand @heelc29 @CSGoat0 ? Unfortunately, I can't.
media_source/plg_editors_codemirror/builder.mjs
uri: modulePath.replace('.js', '.min.js').replace(/\\/g, '/'),@heelc29 would this resolve the issue? I opened a PR (joomdonation#6) against @joomdonation branch, but maybe you could test it out beforehand @heelc29 @CSGoat0 ? Unfortunately, I can't.
media_source/plg_editors_codemirror/builder.mjs
uri: modulePath.replace('.js', '.min.js').replace(/\\/g, '/'),My original error was on a new Joomla 6 clone; it was composer error that is not related to this PR. This is another issue that have just shown up. I tried a lot to run npm ci and npm install on a new cloned joomla 6.2
git clone -b 6.2-dev https://github.com/YourForkLinkOrJoomlaMainLink and every time i get you should run composer install first even after running composer install multiple times and clone multiple times in new different folders.
When I tried this PR on my working version of 6.2, the npm ci worked correctly with no errors.
I can confirm that this PR break the codemirror files and it doesn't work correctly on the site just as @heelc29 have said.
I couldn't replicate ENOENT issue reported by @brianteeman, I ran npm ci on 2 scenarios:
• When there is no media folder at all
• When there is an empty media folder
both scenarios, the npm ci command ran correctly with no issues except the codemirror issue.
codemirrornpm issue on a new 6.2 clone if someone can confirmENOENT issueMy original error was on a new Joomla 6 clone; it was composer error that is not related to this PR. This is another issue that have just shown up. I tried a lot to run npm ci and npm install on a new cloned joomla 6.2
git clone -b 6.2-dev https://github.com/YourForkLinkOrJoomlaMainLink and every time i get you should run composer install first even after running composer install multiple times and clone multiple times in new different folders.
When I tried this PR on my working version of 6.2, the npm ci worked correctly with no errors.
I can confirm that this PR break the codemirror files and it doesn't work correctly on the site just as @heelc29 have said.
I couldn't replicate ENOENT issue reported by @brianteeman, I ran npm ci on 2 scenarios:
• When there is no media folder at all
• When there is an empty media folder
both scenarios, the npm ci command ran correctly with no issues except the codemirror issue.
codemirrornpm and composer issue on a new 6.2 clone if someone can confirmENOENT issueMy original error was on a new Joomla 6 clone; it was composer error that is not related to this PR. This is another issue that have just shown up. I tried a lot to run npm ci and npm install on a new cloned joomla 6.2
git clone -b 6.2-dev https://github.com/YourForkLinkOrJoomlaMainLink and every time i get you should run composer install first even after running composer install multiple times and clone multiple times in new different folders.
When I tried this PR on my working version of 6.2, the npm ci worked correctly with no errors.
I can confirm that this PR break the codemirror files and it doesn't work correctly on the site just as @heelc29 have said.
I couldn't replicate ENOENT issue reported by @brianteeman, I ran npm ci on 2 scenarios:
• When there is no media folder at all
• When there is an empty media folder
both scenarios, the npm ci command ran correctly with no issues except the codemirror issue.
codemirrornpm and composer issue on a new 6.2 clone if someone can confirmENOENT issueThis update is based on a meeting with @LadySolveig, Thanks to her.
@LadySolveig I have tried this line uri: modulePath.replace('.js', '.min.js').replace(/\\/g, '/'), It replaces every \\ with / but the codemirror still broken somehow.
i have re-run the test about 20 times and I cannot repeat the error I got before. weird but I guess its one of those things.
I can confirm the codemirror slash issue reported by @heelc29
I tried the fix from @LadySolveig and that resolved the slash issue
I tested codemirror inside Joomla and it appeared to run correctly
@joomdonation can you include the fix from @CSGoat0 / @LadySolveig ? - Thank you all - i hope this is the final fix...
i have re-run the test about 20 times and I cannot repeat the error I got before. weird but I guess its one of those things.
I can confirm the codemirror slash issue reported by @heelc29
I tried the fix from @LadySolveig and that resolved the slash issue
I tested codemirror inside Joomla and it appeared to run correctly
Codemirror will be missing both styling and numbered lines. It won't look like this photo:
If you try to add the version in plg_editors_codemirror/builder.mjs you will get the correct codemirror.
I talked with @LadySolveig, she will open a new PR to replace this one in the morning. She understands the script, so it will be easier for her to make any additional changes if needed. Thanks you all for testing and help.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-05-18 00:30:49 |
| Closed_By | ⇒ | joomdonation |
I have tested this item ✅ successfully on d02d361
Works fine for me on Windows 11
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47789.