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
Cerebro installation fails with unexpected token operator #356
Comments
To clarify whether the issue with AUR package or application itself, could you please confirm if the issue happens during installation, or after installation when starting the app? |
@maximbaz during installation |
I confirm, the error happens to me too during installation. Interestingly though I installed cerebro just two days ago from the same AUR package and it was successful. It is also curious that both @KELiON Looks like some dependency got updated (uglifyjs?) which breaks the build now. As for the transparent window bug, it is tracked in #285 |
@maximbaz 🤔 even if something was updated it should work, because all dependencies are locked in |
That is almost exactly what AUR package is doing, but for the sake of experiment I've just cloned the repo from scratch and ran the following:
And it reproduces, exactly the same error. |
If you have docker, I've recently made a docker image that builds AUR packages, you can try it 🙂
Put |
@KELiON Your builds are failing as well https://travis-ci.org/KELiON/cerebro/builds/250264889 |
@IgnusG yep, started to fail on travis after merging last PR, I didn't find time to fix, I'll try to do it asap |
It seems that |
@enguerran uglify-js doesn't work with new ES syntax, i.e. with arrow functions. But in cerebro we're using uglify-es, that do support it |
Tried to clone repo and reinstall everything from scratch, but still works. Can someone run
/cc @maximbaz |
This seems to be the problem. Clean run, once again.
|
@KELiON I can confirm the latest release of cerebro uses $ npm list | grep uglify
uglify-es@3.0.15
│ ├─┬ uglify-js@2.8.27
│ │ ├── uglify-to-browserify@1.0. $ yarn list | grep uglify
uglify-es@3.0.15
├─ uglify-js@2.8.27
│ ├─ uglify-to-browserify@~1.0.0
├─ uglify-to-browserify@1.0.2
│ ├─ uglify-js@^2.8. |
It's fascinating, I mean we packed the release sources in an archive, locked dependencies versions, I'm 100% positive it used to work just two weeks ago on my own laptop with the same OS, and now the same archive cannot correctly be installed, and the issue reproduces every single time... I'm very keen to see the solution for this bug, what else has to be locked to ensure that a given sources archive will always be able to build successfully in the future. |
As a temporary solution I fixed path to uglify binary ( |
That works 👍 To state the obvious, once its merged, |
Issue
Installing via AUR results in following error message with both
cerebro
andcerebro-git
package:The text was updated successfully, but these errors were encountered: