Open hatton opened 4 years ago
FYI:
I get the application to "run" when I:
$ yarn
$ yarn lingui-compile
$ yarn dev
I don't know what the screen is supposed to look like. If I make screenshots for the readme, do you want them?
I don't know what sort of interactivity is supposed to happen. Are the language names in Unicode? the second one is garbled... looks like an encoding error. Is the People menu supposed to be grayed out when one is not on the people tab? Are the language names supposed to be automatically added if one provides a language code?
here is the errors I get when I run yarn package
: https://gist.github.com/HughP/272ab7da284a3e4767f02160129f8df6
The email thing is fixed. The AppImage that is produced in the release/
folder looks usable.
Remaining known issues:
I've updated the lameta-unofficial snap package to the latest 2.3.9-beta release. If this route proves to be functionally sound (i.e. I'd like to get actual user feedback), I'd be happy to figure out how to roll it into the official project so that there's an auto-built snap package for each release.
I took some personal time to work on getting a linux build. I was only semi-successful, but we can use this issue to track progress.
Had to get node 12 installed... will add that to the readme.
yarn && yarn build && yarn start
runs lameta. In /app/package.json, I had to add a bogus email address... will commit that.yarn && yarn package
fails, but doesn't say why. Something is going wrong withwebpack.config.renderer.production.js
In package.json had to change thebuild-production-renderer
script to instead runwebpack.config.renderer.development.js
That succeeded, and now /release/ has an .AppImage which runs when I click it, and a .deb, which I haven't tried yet.So I think the next step is to get more error information out of webpack to figure out what is going wrong with
webpack.config.renderer.production.js