-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Following CONTRIBUTING.md: npm run test fails, npm run lint script is missing #192
Comments
+1 |
test fails since Nx 15.4 changes the cli architecture. |
The tests need a lot of reworks, and some are broken for quite a long time (unfortunately) |
Count me in @bennymeg , I have fix partially some of the test scripts.
|
Ok, for 15, I'm going to probably write a FULL REWRITE. yes. and this is why The constant issues the current plugin has in terms of testing make it inviable to use it as it is. so I will create a separate branch JUST FOR 15, and work from there. There might be no point in doing the migration from 14 with all the breaking changes it is having. Better to have clear schematics from start. |
please wait a bit until I will release v14 (by the end of this week) and branch from there. |
ok! then I will wait 😂, migration from there should be easy. I would suggest to take a look into the vite plugin for electron. probably a good option for rewrite: https://github.com/alex8088/electron-vite |
According to
CONTRIBUTING.md
after cloning the repo and runningnpm ci
npm run test
fails andnpm run lint
doesn't work because there is notlint
in thescripts
section.To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/bennymeg/nx-electron.git
cd nx-electron && npm link
npm ci
npm run test
npm run lint
lint
in thescripts
sectionExpected behavior
Without any changes all tests should run without any errors.
Either add
lint
to thescripts
section or remove the part about linting the forked project fromCONTRIBUTING.md
file.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: