-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Can't Start on Windows: The module at "/pad_utils" does not exist #456
Comments
When have you downloaded that file? Afaik @cweider cweider fixed this bug today. The windows zip gets rebuild every 6 hours. If the latest download doesn't work try it again later |
Downloaded @ 8:35am PST. I'll re-download in an hour or two and close the issue if it's fixed. (thanks for the quick reply.) |
@sufyit, Window file paths are causing trouble ( |
Thanks! I downloaded a fresh install this morning and it's working GREAT! |
Great work everyone :) Apologies to @sufyit for the headache :) |
This upgrade solves the high-severity vulnerabilities regarding https-proxy-agent that were still present in 8e6bca4. The output of `npm audit` goes from this: found 29 vulnerabilities (3 low, 26 high) in 13338 scanned packages run `npm audit fix` to fix 4 of them. 1 vulnerability requires semver-major dependency updates. 24 vulnerabilities require manual review. See the full report for details. To this: found 5 vulnerabilities (3 low, 2 high) in 13338 scanned packages 1 vulnerability requires semver-major dependency updates. 4 vulnerabilities require manual review. See the full report for details. Changelog: - https://github.com/npm/cli/releases 6.13.1 (2019-11-18) BUG FIXES 938d6124d #472 fix(fund): support funding string shorthand (@ruyadorno) b49c5535b #471 should not publish tap-snapshot folder (@ruyadorno) 3471d5200 #253 Add preliminary WSL support for npm and npx (@infinnie) 3ef295f23 #486 print quick audit report for human output (@isaacs) TESTING dbbf977ac #278 added workflow to trigger and run benchmarks (@mikemimik) b4f5e3825 #457 feat(docs): adding tests and updating docs to reflect changes in registry teams API. (@nomadtechie) 454c7dd60 #456 fix git configs for git 2.23 and above (@isaacs) DEPENDENCIES 661d86cd2 [email protected] (@claudiahdz) 6.13.0 (2019-11-05) NEW FEATURES 4414b06d9 #273 add fund command (@ruyadorno) BUG FIXES e4455409f #281 delete ps1 files on package removal (@NoDocCat) cd14d4701 #279 update supported node list to remove v6.0, v6.1, v9.0 - v9.2 (@ljharb) DEPENDENCIES a37296b20 [email protected] d3cb3abe8 [email protected] TESTING 688cd97be #272 use github actions for CI (@JasonEtco) 9a2d8af84 #240 Clean up some flakiness and inconsistency (@isaacs)
I just downloaded http://etherpad.org/etherpad-lite-win.zip
extracted it to c:\etherpad and ran the start.bat
I'm getting the error below. Any ideas how to fix this? with googling I came across: a similar issue on OSX: https://github.com/Pita/etherpad-lite/issues/451
(I'm running Windows 7 64bit, running command prompt as Admin.)
Thanks for you help!
-David
C:\etherpad>cd node
C:\etherpad\node>..\bin\node server.js
�[32m[2012-02-16 12:18:39.725] [INFO] console - �[39mYour Etherpad Lite git version is 9ca914f
�[32m[2012-02-16 12:18:39.727] [INFO] console - �[39mReport bugs at https://github.com/Pita/etherpad-lite/issues
node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: The module at "/pad_utils" does not exist.
at _designatedRequire (C:\etherpad\node_modules\require-kernel\kernel.js:570:15)
at designatedRequire (C:\etherpad\node_modules\require-kernel\kernel.js:589:30)
at requireRelative (C:\etherpad\node_modules\require-kernel\kernel.js:595:12)
at Object.require (C:\etherpad\node_modules\require-kernel\kernel.js:630:16)
at Object. (C:\etherpad\node\db\ReadOnlyManager.js:25:31)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Module.require (module.js:357:17)
The text was updated successfully, but these errors were encountered: