MarkCavalli

Open source Role Play server

Recommended Posts

vor 3 Minuten schrieb FieteGM:

okaz thats works fine. and now the next problem..... I startet cmd in the app folder and write down npm run build. Then came this error>

> [email protected] build C:\Users\Administrator\Desktop\RageMP - Server RP\server-files
> webpack --mode=production

'webpack' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `webpack --mode=production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2019-01-20T17_46_18_519Z-debug.log

whats say the debug log file?

 

Share this post


Link to post
Share on other sites
vor 29 Minuten schrieb FieteGM:

sry but who can i find that ? xD ....

 

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2019-01-20T17_46_18_519Z-debug.log

Share this post


Link to post
Share on other sites
vor 2 Minuten schrieb FieteGM:

oh wow i was very dump.... okay here it is:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build' ]
2 info using [email protected]
3 info using [email protected]
4 warn invalid config registry=""
5 warn invalid config Must be a full url with 'http://'
6 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
7 info lifecycle [email protected]~prebuild: [email protected]
8 info lifecycle [email protected]~build: [email protected]
9 verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true
10 verbose lifecycle [email protected]~build: PATH: C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Administrator\Desktop\RageMP - Server RP\server-files\node_modules\.bin;C:\Python27\;C:\Python27\Scripts;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\dotnet\;C:\Program Files\Git\cmd;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Program Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;C:\Users\Administrator\AppData\Roaming\npm
11 verbose lifecycle [email protected]~build: CWD: C:\Users\Administrator\Desktop\RageMP - Server RP\server-files
12 silly lifecycle [email protected]~build: Args: [ '/d /s /c', 'webpack --mode=production' ]
13 silly lifecycle [email protected]~build: Returned: code: 1  signal: null
14 info lifecycle [email protected]~build: Failed to exec build script
15 verbose stack Error: [email protected] build: `webpack --mode=production`
15 verbose stack Exit status 1
15 verbose stack     at EventEmitter.<anonymous> (C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
15 verbose stack     at EventEmitter.emit (events.js:188:13)
15 verbose stack     at ChildProcess.<anonymous> (C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
15 verbose stack     at ChildProcess.emit (events.js:188:13)
15 verbose stack     at maybeClose (internal/child_process.js:978:16)
15 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
16 verbose pkgid [email protected]
17 verbose cwd C:\Users\Administrator\Desktop\RageMP - Server RP\server-files\app\server
18 verbose Windows_NT 10.0.14393
19 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
20 verbose node v11.7.0
21 verbose npm  v6.6.0
22 error code ELIFECYCLE
23 error errno 1
24 error [email protected] build: `webpack --mode=production`
24 error Exit status 1
25 error Failed at the [email protected] build script.
25 error This is probably not a problem with npm. There is likely additional logging output above.
26 verbose exit [ 1, true ]

why is the -mode=prodution? it should development

Edited by Geekbee

Share this post


Link to post
Share on other sites
vor 1 Minute schrieb FieteGM:

okay and who can i change this to .mode=development ? .... i ask this because i wount to change the wrong

its in package.json

Share this post


Link to post
Share on other sites
6 минут назад, Archie сказал:

@MarkCavalliПодскажи,выходит когда заправку делаюepmd5tbmhL0.jpg

you should set filling coords

Share this post


Link to post
Share on other sites

Есть ли тут команда для назначения лидера фракции

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.