java.lang.RuntimeException

com.google.javascript.jscomp.CompilerOptionsPreprocessor$InvalidOptionsException: The jQuery pass and the Closure pass cannot both be enabled.

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3

  • via GitHub by anonymousandrew
    ,
  • Stack trace

    • java.lang.RuntimeException: com.google.javascript.jscomp.CompilerOptionsPreprocessor$InvalidOptionsException: The jQuery pass and the Closure pass cannot both be enabled. at com.google.javascript.jscomp.CompilerExecutor.runInCompilerThread(CompilerExecutor.java:126) at com.google.javascript.jscomp.Compiler.runInCompilerThread(Compiler.java:740) at com.google.javascript.jscomp.Compiler.compile(Compiler.java:710) at com.google.javascript.jscomp.Compiler.compile(Compiler.java:680) at com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:1080) at com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:492) at com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:1866) Caused by: com.google.javascript.jscomp.CompilerOptionsPreprocessor$InvalidOptionsException: The jQuery pass and the Closure pass cannot both be enabled. at com.google.javascript.jscomp.CompilerOptionsPreprocessor.preprocess(CompilerOptionsPreprocessor.java:74) at com.google.javascript.jscomp.Compiler.compileInternal(Compiler.java:746) at com.google.javascript.jscomp.Compiler.access$000(Compiler.java:84) at com.google.javascript.jscomp.Compiler$2.call(Compiler.java:713) at com.google.javascript.jscomp.Compiler$2.call(Compiler.java:710) at com.google.javascript.jscomp.CompilerExecutor$2.call(CompilerExecutor.java:91) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.