Open zeuner opened 3 years ago
@Kritten Can you comment?
Hi @zeuner,
I know it's far from perfect but just ignore those errors :)
All those errors are from eslint, a javascript code linter.
Despite the errors you should have a new folder with the compiled frontend at frontend/dist/
after executing the command.
Can we suppress them?
@zeuner please try to build the master branch again. I updated some packages and removed Eslint and Typescript warnings/errors.
Thanks, npm run build
looks nice and clean now.
The build can be completed. The npm run parcel_annotate_build
and npm run parcel_sandbox_hit_build
steps throw errors, though:
> mturk@1.0.0 parcel_annotate_build /home/mturk/mturk-manager/frontend
> parcel build ./annotate/index_annotate.ts -d ./dist
error: unknown option '-d'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mturk@1.0.0 parcel_annotate_build: `parcel build ./annotate/index_annotate.ts -d ./dist`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mturk@1.0.0 parcel_annotate_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! /home/mturk/.npm/_logs/2021-07-25T23_29_31_582Z-debug.log
@Kritten Can they also be disregarded?
I'm unable to build mturk-manager from source. From the comments, I assume that
deploy.sh
is supposed to achieve this. It works for the backend part. For the frontend part, it fails right on the first commandnpm run build
:[...]
Since there are working builds available from docker, I assume this is a documentation issue. Maybe it will even suffice to specify build prerequisites.