-
Notifications
You must be signed in to change notification settings - Fork 16
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
Server crash 1-2 ticks after start #36
Comments
This isn't the experience that other users are having. I tested this from scratch using a fresh local account and it's working fine over here. Since it's not fixing itself when you rewind to an old commit it really seems like this is something local to your computer. Please do some digging and see if you can figure this out. |
i checked for older version of source-map package - no change for now. |
reinstalling node (using nvm) to newest 16.8.0 version did not help after commenting out the source-map part that caused the crash, i started getting
|
sam happens if i change
to
quite out of ideas, i've also tried installing on different drive, but same bucket of issues |
I have been experiencing the same issue on the following environment
I got no mods installed, just freshly cloned this repo and follow the steps: npm install
npm run build
npx xxscreeps import
npx xxscreeps start Here is what I get: $ npx xxscreeps start
🌎 Listening
Abandoning intents in rooms [W1N1, W1N9, W9N1, W9N9] for tick 1
Tick 1 ran in 5021ms; avg: 5020.73ms
node:internal/process/esm_loader:74
internalBinding('errors').triggerUncaughtException(
^
Error [ERR_UNHANDLED_ERROR]: Unhandled error. ("export 'install' (imported as 'SourceMap') was not found in 'source-map-support' (module has no exports)")
at __node_internal_captureLargerStackTrace (node:internal/errors:456:5)
at __node_internal_addCodeToName (node:internal/errors:191:9)
at new NodeError (node:internal/errors:363:5)
at Worker.emit (node:events:383:17)
at Worker.[kOnErrorMessage] (node:internal/worker:298:10)
at Worker.[kOnMessage] (node:internal/worker:309:37)
at MessagePort.<anonymous> (node:internal/worker:210:57)
at MessagePort.[nodejs.internal.kHybridDispatch] (node:internal/event_target:461:20)
at MessagePort.exports.emitMessage (node:internal/per_context/messageport:23:28) {
code: 'ERR_UNHANDLED_ERROR',
context: "export 'install' (imported as 'SourceMap') was not found in 'source-map-support' (module has no exports)"
} |
When I actually remove the call to EDIT: It's same as you experienced here #36 (comment) |
Hmm, had an old install and I fetched the latest code and got this error
I was using "webpack": "5.51.1" and stumpled upon this issue webpack/webpack#8302 npm outdated lists The issue I found earlier mentions webpack/webpack-sources#41 whitespaces causing invalid source maps and ESLint is whining about LF vs CLRF (I am on windows) As far as I can see source-map-support should be exporting an install method, but perhaps it is not properly picked up by webpack? Changing it to found this open issue on nodejs nodejs/help#3163 that links to this https://nodejs.org/api/esm.html#esm_mandatory_file_extensions that mentions this https://github.com/nodejs/cjs-module-lexer/tree/1.2.2#parsing-examples is it simply because no exports are detected from the source-map-support.js for some reason? Found this issue as well on the source-map-support repo Cannot find module 'source-map' from 'source-map-support.js' The last thing I've done is deleting the @laverdet If you can find some free time to perhaps help with debugging and solving this, windows users might be able to help with progress on the project :) I'll gladly assist in debugging it, I just have no clue as to what else we can do to figure it out. |
I got the same if I removed
I found this issue an issue saying
I tried fiddling around and disabling things but that is a deep rabithole, it seems a lot like something is wonky in regards to webpack loading modules that perhaps are writtin in a specific way and use a specific module loader? at least in windows. |
Okay so using dev containers with visual studio code form this PR #48 allows me to run the server. I do however get the following errors after 2 ticks, the server recovers and continues though. could they perhaps be related, or is that another issue?
|
I do wonder if the engine error |
win10, Node 16.6.1, running via VS 2019 terminal
with and without default mods, tick speed does not change anything either:
on clean copy of xxscreeps,
after
running
npx xxscreeps start
starts server, but after 1-3 long ticks (configured to 1s in config)an error is thrown:
on subsequent tries of
npx xxscreeps start
the error pops immediately (no ticks processed)problem seems to steam from
source-map.ts
i tried installing it globally but nothing changed
issue started around 30 Aug so i tried some older commits
bae0f5ea00d557c49161a8fb9cc416d4c1a566f8
andb104d94c85f7f8976a86568d1dfea4db1d0972d7
but nothing changedThe text was updated successfully, but these errors were encountered: