alinGmail / LiveMock

LiveMock is a comprehensive tool for API development and testing, offering mock data, request proxying, and logging, to streamline workflows and track traffic.
Apache License 2.0
553 stars 84 forks source link

Encounter error while trying to run electron #22

Closed CaptainJon closed 2 months ago

CaptainJon commented 4 months ago

yarn workspace desktop start

image

alinGmail commented 4 months ago

Can you provide more information? For example how to reproduce this problem

alinGmail commented 4 months ago

try to build the core sub project first, cd to the core folder, run 'yarn run tsc'

CaptainJon commented 4 months ago

try to build the core sub project first, cd to the core folder, run 'yarn run tsc'

yeah, it works now, then how to start the electron? i tried cd to the desktop fold and run " yarn start" or "yarn dev", the electron app shows but nothing on it. it is blank. can you show the step? image

alinGmail commented 4 months ago

you need to build the project first, in the desktop folder, run 'yarn run tsc' , then 'yarn run vite' and then 'yarn run electron'.

CaptainJon commented 4 months ago

you need to build the project first, in the desktop folder, run 'yarn run tsc' , then 'yarn run vite' and then 'yarn run electron'.

nice, it's working now, i guess if i want to build the electron, just run "yarn run build"?

CaptainJon commented 4 months ago

you need to build the project first, in the desktop folder, run 'yarn run tsc' , then 'yarn run vite' and then 'yarn run electron'.

when I try "yarn run electron", the apps shows and works well (add exceptations works, modify expectations works, modify project info works), but the command shows errors below:

image

when I tried to start the server, error pops out: image

and the commands adds some warnning or error i dunno: image

alinGmail commented 4 months ago

i have no idea about the ssl error. but it look like have nothing to do with the server start fail. you can change the projectHandler.js code in dist-electron folder. in line 137. it may be look like the code above

server.once("error", (error) => { // res.status(500); throw new common_1.ServerError(500, "server start fail"); }); add some code to log the error to see what happen.