closure-compiler | A JavaScript checker and optimizer.

by google Java Version: Current License: Apache-2.0

Download this library from

kandi X-RAY | closure-compiler Summary

closure-compiler is a Java library. closure-compiler has a Permissive License and it has medium support. However closure-compiler has 785 bugs, it has 5 vulnerabilities and it build file is not available. You can download it from GitHub, Maven.

The Closure Compiler is a tool for making JavaScript download and run faster. It is a true compiler for JavaScript. Instead of compiling from a source language to machine code, it compiles from JavaScript to better JavaScript. It parses your JavaScript, analyzes it, removes dead code and rewrites and minimizes what's left. It also checks syntax, variable references, and types, and warns about common JavaScript pitfalls.

Support

Quality

Security

License

Reuse

kandi-support Support

closure-compiler has a medium active ecosystem.
It has 6402 star(s) with 1112 fork(s). There are 244 watchers for this library.
It had no major release in the last 12 months.
There are 844 open issues and 1944 have been closed. On average issues are closed in 63 days. There are 5 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of closure-compiler is current.

closure-compiler Support

Best in #Java

Average in #Java

closure-compiler Support

Best in #Java

Average in #Java

quality kandi Quality

closure-compiler has 785 bugs (1 blocker, 7 critical, 747 major, 30 minor) and 15324 code smells.

closure-compiler Quality

Best in #Java

Average in #Java

closure-compiler Quality

Best in #Java

Average in #Java

security Security

closure-compiler has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
closure-compiler code analysis shows 5 unresolved vulnerabilities (0 blocker, 0 critical, 0 major, 5 minor).
There are 29 security hotspots that need review.

closure-compiler Security

Best in #Java

Average in #Java

closure-compiler Security

Best in #Java

Average in #Java

license License

closure-compiler is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.

closure-compiler License

Best in #Java

Average in #Java

closure-compiler License

Best in #Java

Average in #Java

build Reuse

closure-compiler releases are not available. You will need to build from source code and install.
Deployable package is available in Maven.
closure-compiler has no build file. You will be need to create the build yourself to build the component from source.
Installation instructions, examples and code snippets are available.
closure-compiler saves you 894442 person hours of effort in developing the same functionality from scratch.
It has 421484 lines of code, 33804 functions and 1883 files.
It has high code complexity. Code complexity directly impacts maintainability of the code.

closure-compiler Reuse

Best in #Java

Average in #Java

closure-compiler Reuse

Best in #Java

Average in #Java

Top functions reviewed by kandi - BETA

kandi has reviewed closure-compiler and discovered the below as its top functions. This is intended to give you an instant insight into closure-compiler implemented functionality, and help decide if they suit your requirements.

Parse an annotation .
Convert a double to a string .
Parse a regular expression .
Visits a node .
Initializes native types .
Builds the passes for optimizations .
Translates node kind .
Deserialize a single node .
Generates a string representation of a JSDoc .
Try to minimize the given IF condition .

closure-compiler Key Features

Consult the FAQ to make sure that the behaviour you would like isn't specifically excluded (such as string inlining).

Make sure someone hasn't requested the same thing. See the list of known issues.

Read up on what type of feature requests are accepted.

Submit your request as an issue.

closure-compiler Examples and Code Snippets

See all related Code Snippets

Getting Started

Copy

Download

yarn global add google-closure-compiler
# OR
npm i -g google-closure-compiler

Basic usage

Copy

Download

google-closure-compiler --js file.js --js_output_file file.out.js

NodeJS API

Copy

Download

import closureCompiler from 'google-closure-compiler';
const { compiler } = closureCompiler;

new compiler({
  js: 'file-one.js',
  compilation_level: 'ADVANCED'
});

Compiling Multiple Scripts

Copy

Download

google-closure-compiler in1.js in2.js in3.js --js_output_file out.js

Building from a terminal

Copy

Download

# bazelisk build //:compiler_unshaded_deploy.jar
yarn build

# bazelisk build :all
yarn build:all

Testing from a terminal

Copy

Download

# bazelisk test //:all

Running

Copy

Download

# java -jar bazel-bin/compiler_unshaded_deploy.jar [...args]
yarn compile [...args]

JSDoc Mark something as Class after instantiation and define constructor properties

Copy

Download

const Queue_PoolEntry = /** @type {QPE_Opts} */ (mongoose.model('Queue_PoolEntry', 
    Queue_PoolEntrySchema));

let Queue_PoolEntry = mongoose.model('Queue_PoolEntry', 
    Queue_PoolEntrySchema);
if (Queue_PoolEntry && Queue_PoolEntry.id) {
  Queue_PoolEntry = /** @type {QPE_Opts} */ (Queue_PoolEntry)
} else {
  throw new Error('mongoose.model(\'Queue_PoolEntry\', Queue_PoolEntrySchema)'+
      'returned something other than a QPE_Opts' + Queue_PoolEntry);
}

-----------------------

const Queue_PoolEntry = /** @type {QPE_Opts} */ (mongoose.model('Queue_PoolEntry', 
    Queue_PoolEntrySchema));

let Queue_PoolEntry = mongoose.model('Queue_PoolEntry', 
    Queue_PoolEntrySchema);
if (Queue_PoolEntry && Queue_PoolEntry.id) {
  Queue_PoolEntry = /** @type {QPE_Opts} */ (Queue_PoolEntry)
} else {
  throw new Error('mongoose.model(\'Queue_PoolEntry\', Queue_PoolEntrySchema)'+
      'returned something other than a QPE_Opts' + Queue_PoolEntry);
}

How to use use React libraries in ClojureScript

Copy

Download

(ns my-project
  (:require [cljsjs.vis]))

;; accessing vis via js/WhateverGlobalItUses

(ns my-project
  (:require ["vis-network" :as vis]))

;; then use "vis" directly

-----------------------

(ns my-project
  (:require [cljsjs.vis]))

;; accessing vis via js/WhateverGlobalItUses

(ns my-project
  (:require ["vis-network" :as vis]))

;; then use "vis" directly

Angular 2 example app returns error "Cannot read property 'X' of null"

Copy

Download

 {
    "$schema": "./node_modules/@angular/cli/lib/config/schema.json",
    "project": {
        "name": "xyz"
    },
    "apps": [
        {
            "root": "src",
            "outDir": "dist",
            "assets": [
                "assets",
                "favicon.ico"
            ],
            "index": "index.html",
            "main": "main.ts",
            "polyfills": "polyfills.ts",
            "test": "test.ts",
            "tsconfig": "tsconfig.app.json",
            "testTsconfig": "tsconfig.spec.json",
            "prefix": "app",
            "styles": [
                "assets/css/styles.css"

            ],
            "scripts": [
                "assets/js/project.js"      

            ],
            "environmentSource": "environments/environment.ts",
            "environments": {
                "dev": "environments/environment.ts",
                "prod": "environments/environment.prod.ts"
            }
        }
    ],
    "e2e": {
        "protractor": {
            "config": "./protractor.conf.js"
        }
    },
    "lint": [
        {
            "project": "src/tsconfig.app.json"
        },
        {
            "project": "src/tsconfig.spec.json"
        },
        {
            "project": "e2e/tsconfig.e2e.json"
        }
    ],
    "test": {
        "karma": {
            "config": "./karma.conf.js"
        }
    },
    "defaults": {
        "styleExt": "css",
        "component": {}
    }
}

What is the correct jsdoc type annotation for a try..catch identifier?

Copy

Download

try {throw new Error();} catch (/** @type {Error}*/whatIsMyType) {
  console.error(whatIsMyType.message);
}

try { throw new Error(); } catch (e: Error) {}

try {
  throw new CustomError();
}
catch (err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

class CustomError extends Error {
  constructor() {
    super();
    /** @type {string} */
    this.aPropThatIndeedExistsInCustomError = '';
    throw new Error('Not so fast!');  // The evil part is here
  }
}


try {
  throw new CustomError();
}
catch (/**  @type {CustomError} */err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

-----------------------

try {throw new Error();} catch (/** @type {Error}*/whatIsMyType) {
  console.error(whatIsMyType.message);
}

try { throw new Error(); } catch (e: Error) {}

try {
  throw new CustomError();
}
catch (err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

class CustomError extends Error {
  constructor() {
    super();
    /** @type {string} */
    this.aPropThatIndeedExistsInCustomError = '';
    throw new Error('Not so fast!');  // The evil part is here
  }
}


try {
  throw new CustomError();
}
catch (/**  @type {CustomError} */err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

-----------------------

try {throw new Error();} catch (/** @type {Error}*/whatIsMyType) {
  console.error(whatIsMyType.message);
}

try { throw new Error(); } catch (e: Error) {}

try {
  throw new CustomError();
}
catch (err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

class CustomError extends Error {
  constructor() {
    super();
    /** @type {string} */
    this.aPropThatIndeedExistsInCustomError = '';
    throw new Error('Not so fast!');  // The evil part is here
  }
}


try {
  throw new CustomError();
}
catch (/**  @type {CustomError} */err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

-----------------------

try {throw new Error();} catch (/** @type {Error}*/whatIsMyType) {
  console.error(whatIsMyType.message);
}

try { throw new Error(); } catch (e: Error) {}

try {
  throw new CustomError();
}
catch (err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

class CustomError extends Error {
  constructor() {
    super();
    /** @type {string} */
    this.aPropThatIndeedExistsInCustomError = '';
    throw new Error('Not so fast!');  // The evil part is here
  }
}


try {
  throw new CustomError();
}
catch (/**  @type {CustomError} */err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

lein uberjar - not setting main class properly?

Copy

Download

  :main my.service.runner

ERROR - [JSC_UNDEFINED_VARIABLE] variable previousPage is undeclared - Google Closure Compiler

Copy

Download

for (var i = 0; i < individualPagesArray.length; i++) {
   document.getElementById("numbers").innerHTML += `<button onclick=showCurrentPage(${i+1})>` + individualPagesArray[i] + `</button>`;
}

window.showCurrentPage = (i) => {

window['showCurrentPage'] = (i) => {

-----------------------

for (var i = 0; i < individualPagesArray.length; i++) {
   document.getElementById("numbers").innerHTML += `<button onclick=showCurrentPage(${i+1})>` + individualPagesArray[i] + `</button>`;
}

window.showCurrentPage = (i) => {

window['showCurrentPage'] = (i) => {

-----------------------

for (var i = 0; i < individualPagesArray.length; i++) {
   document.getElementById("numbers").innerHTML += `<button onclick=showCurrentPage(${i+1})>` + individualPagesArray[i] + `</button>`;
}

window.showCurrentPage = (i) => {

window['showCurrentPage'] = (i) => {

strange object property behavior with closure compiler ADVANCED_OPTIMIZATIONS

Copy

Download

/**
 * @interface
 */
function AppProps() {}

/**
 * @type {string}
 */
AppProps.prototype.version;

/**
 * @type {string}
 */
AppProps.prototype.api_host;

/**
 * 
 * @param {AppProps} props 
 */
window['app'] = function(props) {
    props = props || {};
    console.log("props.api_host = ", props.api_host);
    console.log("props['api_host'] = ", props['api_host']);
};

-----------------------

/**
 * @interface
 */
function AppProps() {}

/**
 * @type {string}
 */
AppProps.prototype.version;

/**
 * @type {string}
 */
AppProps.prototype.api_host;

/**
 * 
 * @param {AppProps} props 
 */
window['app'] = function(props) {
    props = props || {};
    console.log("props.api_host = ", props.api_host);
    console.log("props['api_host'] = ", props['api_host']);
};

google-closure-compiler basic process example

Copy

Download

const ClosureCompiler = require('google-closure-compiler').jsCompiler;
const {writeFile, readFileSync} = require('fs');

const closureCompiler = new ClosureCompiler({
  compilation_level: 'ADVANCED'
});
let src = readFileSync('a.js', 'UTF-8');
const compilerProcess = closureCompiler.run([{
 path: './',
 src: src,
 sourceMap: null
}], (exitCode, stdOut, stdErr) => {
  stdOut.map((fileResults) => {
    writeFile(fileResults.path, fileResults.src, () => {});
  });
});

console.log('hello world!')

console.log("hello world!");

-----------------------

const ClosureCompiler = require('google-closure-compiler').jsCompiler;
const {writeFile, readFileSync} = require('fs');

const closureCompiler = new ClosureCompiler({
  compilation_level: 'ADVANCED'
});
let src = readFileSync('a.js', 'UTF-8');
const compilerProcess = closureCompiler.run([{
 path: './',
 src: src,
 sourceMap: null
}], (exitCode, stdOut, stdErr) => {
  stdOut.map((fileResults) => {
    writeFile(fileResults.path, fileResults.src, () => {});
  });
});

console.log('hello world!')

console.log("hello world!");

-----------------------

const ClosureCompiler = require('google-closure-compiler').jsCompiler;
const {writeFile, readFileSync} = require('fs');

const closureCompiler = new ClosureCompiler({
  compilation_level: 'ADVANCED'
});
let src = readFileSync('a.js', 'UTF-8');
const compilerProcess = closureCompiler.run([{
 path: './',
 src: src,
 sourceMap: null
}], (exitCode, stdOut, stdErr) => {
  stdOut.map((fileResults) => {
    writeFile(fileResults.path, fileResults.src, () => {});
  });
});

console.log('hello world!')

console.log("hello world!");

-----------------------

const ClosureCompiler = require('google-closure-compiler').jsCompiler;
const { writeFile } = require('fs');

const closureCompiler = new ClosureCompiler({
    js:['a.js','a1.js'],
    js_output_file: 'out.js'
});

const compilerProcess = closureCompiler.run([{
    path: './',
}], (exitCode, stdOut, stdErr) => {
     writeFile(stdOut[0].path, stdOut[0].src,()=>{});
});

command line compiling generates bigger file than the online version

Copy

Download

--language_out=ECMASCRIPT_2015

Clojure + Clojurescript app on Heroku: dependencies of npm packages not getting installed when deploying app

Copy

Download

FROM openjdk:8-alpine
COPY target/uberjar/getfluentspanish.jar /getfluentspanish/app.jar
EXPOSE 3000
CMD ["java", "-jar", "/getfluentspanish/app.jar"]

See all related Code Snippets

Community Discussions

Trending Discussions on closure-compiler

JSDoc Mark something as Class after instantiation and define constructor properties
How to use use React libraries in ClojureScript
Does react-native optimize JavaScript code?
Google Closure Compiler Output Hosting?
Angular 2 example app returns error "Cannot read property 'X' of null"
What is the correct jsdoc type annotation for a try..catch identifier?
lein uberjar - not setting main class properly?
ERROR - [JSC_UNDEFINED_VARIABLE] variable previousPage is undeclared - Google Closure Compiler
strange object property behavior with closure compiler ADVANCED_OPTIMIZATIONS
google-closure-compiler basic process example

Trending Discussions on closure-compiler

QUESTION

JSDoc Mark something as Class after instantiation and define constructor properties

Asked 2020-Aug-27 at 15:09

I have mongoose create a Model(class) for me, and I would like to have the class to have intellisense. The problem is I don't know how to mark something as a class, and how to type the constructor for that class.

Looking at JSDocs' docs they only specify how to type a class at the declaration, not when it already has been instantiated. The @class and @constructor tags don't seem to do anything.

Right now I am getting my intellisense by marking it as a function (which it is under the hood, but it would still be great to have the correct colors in VSC) and defining the params:

/**
 * @typedef QPE_Opts
 * @type {object}
 * @prop {string} id - Id of the user 
 * ...
 */
/**
 * @type {function(QPE_Opts) : mongoose.Model<mongoose.Document, {}> }}
 */
const Queue_PoolEntry = mongoose.model('Queue_PoolEntry', Queue_PoolEntrySchema);

Solution

The solution (Was looking at the JsDocs' Documentation which was not providing enough info, thanks @Graham P Heath for giving the better docs) :

/**
 * @type {function(new:mongoose.Model<mongoose.Document, {}>, QPE_Opts ) }}
 */

ANSWER

Answered 2020-Aug-26 at 14:49

If you are sure of the type of an object you can type cast it:

const Queue_PoolEntry = /** @type {QPE_Opts} */ (mongoose.model('Queue_PoolEntry', 
    Queue_PoolEntrySchema));

In situations where you can't actually be sure of the returned type casting may be a code smell. In that case: use code to determine the validity of your type assertion by checking the object for expected properties, and only then casting it.

let Queue_PoolEntry = mongoose.model('Queue_PoolEntry', 
    Queue_PoolEntrySchema);
if (Queue_PoolEntry && Queue_PoolEntry.id) {
  Queue_PoolEntry = /** @type {QPE_Opts} */ (Queue_PoolEntry)
} else {
  throw new Error('mongoose.model(\'Queue_PoolEntry\', Queue_PoolEntrySchema)'+
      'returned something other than a QPE_Opts' + Queue_PoolEntry);
}

Source https://stackoverflow.com/questions/63584790

QUESTION

How to use use React libraries in ClojureScript

Asked 2020-May-24 at 13:48

I'm trying to use cljsjs/vis in my re-frame / reagent / leiningen project, but getting the error when import this library into namespace.

cljsjs/vis in namespace required but not available

Have tried to use another libraries for charts/data visualizations, but still have same result. It seems something wrong with import JS libraries to clojurescript project.

leiningen project.cljs file

(defproject test1 "0.1.0-SNAPSHOT"
  :dependencies [[org.clojure/clojure "1.10.1"]
                 [org.clojure/clojurescript "1.10.764"
                  :exclusions [com.google.javascript/closure-compiler-unshaded
                               org.clojure/google-closure-library
                               org.clojure/google-closure-library-third-party]]
                 [thheller/shadow-cljs "2.9.3"]
                 [reagent "0.10.0"]
                 [re-frame "0.12.0"]
                 [cljs-ajax "0.7.5"]
                 [cljsjs/vis "4.21.0-1"]]

  :plugins [[lein-shadow "0.2.0"]

            [lein-shell "0.5.0"]]

  :min-lein-version "2.9.0"

  :source-paths ["src/clj" "src/cljs"]

  :clean-targets ^{:protect false} ["resources/public/js/compiled" "target"]


  :shell {:commands {"open" {:windows ["cmd" "/c" "start"]
                             :macosx  "open"
                             :linux   "xdg-open"}}}

  :shadow-cljs {:nrepl {:port 8777}

                :builds {:app {:target :browser
                               :output-dir "resources/public/js/compiled"
                               :asset-path "/js/compiled"
                               :modules {:app {:init-fn test1.core/init
                                               :preloads [devtools.preload]}}

                               :devtools {:http-root "resources/public"
                                          :http-port 8280
                                          }}}}

  :aliases {"dev"          ["with-profile" "dev" "do"
                            ["shadow" "watch" "app"]]
            "prod"         ["with-profile" "prod" "do"
                            ["shadow" "release" "app"]]
            "build-report" ["with-profile" "prod" "do"
                            ["shadow" "run" "shadow.cljs.build-report" "app" "target/build-report.html"]
                            ["shell" "open" "target/build-report.html"]]
            "karma"        ["with-profile" "prod" "do"
                            ["shadow" "compile" "karma-test"]
                            ["shell" "karma" "start" "--single-run" "--reporters" "junit,dots"]]}

  :profiles
  {:dev
   {:dependencies [[binaryage/devtools "1.0.0"]]
    :source-paths ["dev"]}

   :prod {}

}

  :prep-tasks [])

cljs file

(ns my-project
  (:require [cljsjs.vis]))

ANSWER

Answered 2020-May-23 at 22:26

shadow-cljs does not support CLJSJS packages. Instead you install the original npm packages those CLJSJS packages represent and use that directly.

So instead of

(ns my-project
  (:require [cljsjs.vis]))

;; accessing vis via js/WhateverGlobalItUses

you do

(ns my-project
  (:require ["vis-network" :as vis]))

;; then use "vis" directly

The npm version is split into multiple separate packages, so just include whatever you want to use.

The shadow-cljs docs explain using npm packages is much more detail. There is also an older example repo using vis-network.

Source https://stackoverflow.com/questions/61977371

QUESTION

Angular 2 example app returns error "Cannot read property 'X' of null"

Asked 2020-Feb-29 at 22:36

I am new to Angular 2 and I am trying run sample applications from GitHub. I downloaded the sample application.

When I am trying to serve the application, it's giving me the following error as shown below in the screen shot:

How can I resolve the error?

package.json

{
  "name": "material2-srcs",
  "description": "Material Design components for Angular",
  "homepage": "https://github.com/angular/material2",
  "bugs": "https://github.com/angular/material2/issues",
  "repository": {
    "type": "git",
    "url": "https://github.com/angular/material2.git"
  },
  "scripts": {
    "postinstall": "ngc -p angular.tsconfig.json",
    "build": "gulp :publish:build-releases",
    "demo-app": "gulp serve:devapp",
    "test": "gulp test",
    "tslint": "gulp lint",
    "stylelint": "gulp lint",
    "e2e": "gulp e2e",
    "deploy": "gulp deploy:devapp",
    "webdriver-manager": "webdriver-manager",
    "docs": "gulp docs",
    "api": "gulp api-docs"
  },
  "version": "5.0.1",
  "license": "MIT",
  "engines": {
    "node": ">= 5.4.1"
  },
  "dependencies": {
    "@angular/animations": "^5.1.1",
    "@angular/common": "^5.1.1",
    "@angular/compiler": "^5.1.1",
    "@angular/compiler-cli": "^5.1.1",
    "@angular/core": "^5.1.1",
    "@angular/forms": "^5.1.1",
    "@angular/http": "^5.1.1",
    "@angular/platform-browser": "^5.1.1",
    "@angular/platform-browser-dynamic": "^5.1.1",
    "@angular/platform-server": "^5.1.1",
    "@angular/router": "^5.1.1",
    "core-js": "^2.4.1",
    "rxjs": "^5.5.5",
    "systemjs": "0.19.43",
    "tsickle": "^0.24.x",
    "tslib": "^1.7.1",
    "typescript": "^2.6.2",
    "zone.js": "^0.8.12"
  },
  "devDependencies": {
    "@angular/bazel": "~5.1.0",
    "@angular/compiler-cli": "~5.1.0",
    "@angular/http": "~5.1.0",
    "@angular/platform-browser-dynamic": "~5.1.0",
    "@angular/platform-server": "~5.1.0",
    "@angular/router": "~5.1.0",
    "@angular/upgrade": "^5.0.1",
    "@bazel/ibazel": "^0.1.1",
    "@google-cloud/storage": "^1.1.1",
    "@types/chalk": "^0.4.31",
    "@types/fs-extra": "^4.0.3",
    "@types/glob": "^5.0.33",
    "@types/gulp": "3.8.32",
    "@types/hammerjs": "^2.0.35",
    "@types/jasmine": "^2.6.0",
    "@types/merge2": "^0.3.30",
    "@types/minimist": "^1.2.0",
    "@types/node": "^7.0.21",
    "@types/run-sequence": "^0.0.29",
    "autoprefixer": "^6.7.6",
    "axe-core": "^2.3.1",
    "axe-webdriverjs": "^1.1.1",
    "chalk": "^1.1.3",
    "dgeni": "^0.4.9",
    "dgeni-packages": "^0.22.0",
    "firebase": "^4.0.0",
    "firebase-admin": "^5.0.0",
    "firebase-tools": "^3.11.0",
    "fs-extra": "^3.0.1",
    "glob": "^7.1.2",
    "google-closure-compiler": "20170409.0.0",
    "gulp": "^3.9.1",
    "gulp-clean": "^0.3.2",
    "gulp-clean-css": "^3.3.1",
    "gulp-cli": "^1.3.0",
    "gulp-connect": "^5.0.0",
    "gulp-conventional-changelog": "^1.1.3",
    "gulp-dom": "^0.9.17",
    "gulp-flatten": "^0.3.1",
    "gulp-highlight-files": "^0.0.5",
    "gulp-htmlmin": "^3.0.0",
    "gulp-if": "^2.0.2",
    "gulp-markdown": "^1.2.0",
    "gulp-rename": "^1.2.2",
    "gulp-sass": "^3.1.0",
    "gulp-transform": "^2.0.0",
    "gulp-util": "^3.0.8",
    "hammerjs": "^2.0.8",
    "highlight.js": "^9.11.0",
    "http-rewrite-middleware": "^0.1.6",
    "image-diff": "^1.6.3",
    "jasmine-core": "^2.8.0",
    "jsonwebtoken": "^7.4.1",
    "karma": "^1.7.1",
    "karma-browserstack-launcher": "^1.3.0",
    "karma-chrome-launcher": "^2.2.0",
    "karma-coverage": "^1.1.1",
    "karma-firefox-launcher": "^1.0.1",
    "karma-jasmine": "^1.1.0",
    "karma-sauce-launcher": "^1.2.0",
    "karma-sourcemap-loader": "^0.3.7",
    "madge": "^2.2.0",
    "magic-string": "^0.22.4",
    "minimatch": "^3.0.4",
    "minimist": "^1.2.0",
    "moment": "^2.18.1",
    "node-sass": "^4.5.3",
    "protractor": "^5.2.0",
    "request": "^2.83.0",
    "resolve-bin": "^0.4.0",
    "rollup": "^0.41.6",
    "rollup-plugin-alias": "^1.3.1",
    "rollup-plugin-node-resolve": "^3.0.0",
    "run-sequence": "^1.2.2",
    "scss-bundle": "^2.0.1-beta.7",
    "selenium-webdriver": "^3.6.0",
    "sorcery": "^0.10.0",
    "stylelint": "^7.12.0",
    "ts-node": "^3.0.4",
    "tsconfig-paths": "^2.3.0",
    "tslint": "^5.8.0",
    "tsutils": "^2.6.0",
    "typescript": "~2.5.2",
    "uglify-js": "^2.8.14",
    "web-animations-js": "^2.2.5"
  }
}

ANSWER

Answered 2017-Dec-15 at 12:24

have u done npm install first?

maybe if u have installed all the necessary component i think u have to run with: npm run serve.dev or npm run test

Source https://stackoverflow.com/questions/47830635

QUESTION

What is the correct jsdoc type annotation for a try..catch identifier?

Asked 2020-Feb-12 at 19:19

When annotating JavaScript sources with JSDoc comments, how do you annotate the type of the try..catch identifier?

try {
  throw new Error();
} catch (whatIsMyType) {
  console.error(whatIsMyType.message);
}

I'm specifically asking for the TypeScript JSDoc dialect, but an answer for the Closure Compiler dialect or even JSDoc itself would be insightful.

I tried (for TypeScript):

try { throw new Error(); } catch (/** @type {Error} */ e) {/*...*/}
try { throw new Error(); } /** @param {Error} e*/ catch (e) {/*...*/}
/** @param {Error} e*/ try { throw new Error(); } catch (e) {/*...*/}

But without success. e has always type any. What would work is

try { throw new Error(); } catch (_e) {
  /** @type {Error} */
  var e = _e;
  // ...
}

And the additional variable would be optimized away by closure compilers advanced mode, but I find that cumbersome and not optimal from a performance perspective (in a dev build) and hope there is a better way (i.e. one where I don't have to create an artificial variable just to annotate the right type).

ANSWER

Answered 2020-Feb-12 at 19:19

try {throw new Error();} catch (/** @type {Error}*/whatIsMyType) {
  console.error(whatIsMyType.message);
}

Is valid according to Closure Compiler.

I don't write much typescript, but I've poked around at a few sources and mostly don't see annotations at the catch level. The few I did see looked like this;

try { throw new Error(); } catch (e: Error) {}

Update:

I think TypeScript has it right in refusing to guarantee a type for the check block. You can throw anything (intentionally or otherwise) within a try block so the compiler can't assure the catch is caught with the right type. In a related answer the solution is that you should check the type in the catch:

try {
  throw new CustomError();
}
catch (err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

credit for ☝

And I (and Robert Martin) encourage this style of type checking even with strong types.

Update 2

I've re-written the example from above into Closure Compiler syntax, and I believe the point remains valid. Even if Closure lets you do the definition from the first example, you probably don't want to (or at least, not only that):

class CustomError extends Error {
  constructor() {
    super();
    /** @type {string} */
    this.aPropThatIndeedExistsInCustomError = '';
    throw new Error('Not so fast!');  // The evil part is here
  }
}


try {
  throw new CustomError();
}
catch (/**  @type {CustomError} */err) {
  console.log('bing');
  if (err instanceof CustomError) {
    console.log(err.aPropThatIndeedExistsInCustomError); //works
    console.log(err.aPropThatDoesNotExistInCustomError); //error as expected
  } else {
    console.log(err); // this could still happen
  }
}

on closure-compiler.appspot

Source https://stackoverflow.com/questions/60164773

QUESTION

lein uberjar - not setting main class properly?

Asked 2020-Jan-03 at 18:04

On a fresh lein new re-frame bc +handler app, if I lein uberjar or lein jar it doesnt seem to set the main class correctly. At the end of the compillation it tells me

Warning: The Main-Class specified does not exist within the jar. It may not be executable as expected. A gen-class directive may be missing in the namespace which contains the main method, or the namespace has not been AOT-compiled.

Here is the server.clj and project.clj that is created using the re-frame +handler template:

server.clj:

(ns bc.server
  (:require [bc.handler :refer [handler]]
            [config.core :refer [env]]
            [ring.adapter.jetty :refer [run-jetty]])
  (:gen-class))

 (defn -main [& args]
   (let [port (Integer/parseInt (or (env :port) "3000"))]
     (run-jetty handler {:port port :join? false})))

project.clj:

(defproject bc "0.1.0-SNAPSHOT"
  :dependencies [[org.clojure/clojure "1.10.1"]
                 [org.clojure/clojurescript "1.10.597"
                  :exclusions [com.google.javascript/closure-compiler-unshaded
                               org.clojure/google-closure-library
                               org.clojure/google-closure-library-third-party]]
                 [thheller/shadow-cljs "2.8.83"]
                 [reagent "0.8.1"]
                 [re-frame "0.10.9"]
                 [compojure "1.6.1"]
                 [yogthos/config "1.1.7"]
                 [ring "1.7.1"]]

  :plugins [
            [lein-shell "0.5.0"]]

  :min-lein-version "2.5.3"

  :source-paths ["src/clj" "src/cljs"]

  :clean-targets ^{:protect false} ["resources/public/js/compiled" "target"]


  :shell {:commands {"open" {:windows ["cmd" "/c" "start"]
                             :macosx  "open"
                             :linux   "xdg-open"}}}

  :aliases {"dev"          ["with-profile" "dev" "do"
                            ["clean"]
                            ["run" "-m" "shadow.cljs.devtools.cli" "watch" "app"]]
            "prod"         ["with-profile" "prod" "do"
                            ["clean"]
                            ["run" "-m" "shadow.cljs.devtools.cli" "release" "app"]]
            "build-report" ["with-profile" "prod" "do"
                            ["clean"]
                            ["run" "-m" "shadow.cljs.devtools.cli" "run" "shadow.cljs.build-report" "app" "target/build-report.html"]
                            ["shell" "open" "target/build-report.html"]]
            "karma"        ["with-profile" "prod" "do"
                            ["clean"]
                            ["run" "-m" "shadow.cljs.devtools.cli" "compile" "karma-test"]
                            ["shell" "karma" "start" "--single-run" "--reporters" "junit,dots"]]}

  :profiles
  {:dev
   {:dependencies [[binaryage/devtools "0.9.11"]]}

   :prod { }

   :uberjar {:source-paths ["env/prod/clj"]
             :omit-source  true
             :main         bc.server
             :aot          [bc.server]
             :uberjar-name "bc.jar"
             :prep-tasks   ["compile" ["prod"]]}
   })

It does generate a jar file when I lein uberjar but when I try to run it it errors out telling me that it does not include a main class.

What am I doing incorrectly?

ANSWER

Answered 2020-Jan-03 at 16:23

You need to tell leiningen what namespace has your main function. In project.clj:

  :main my.service.runner

from: https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L222

Source https://stackoverflow.com/questions/59580237

QUESTION

ERROR - [JSC_UNDEFINED_VARIABLE] variable previousPage is undeclared - Google Closure Compiler

Asked 2019-Dec-17 at 18:47

I'm compiling 2 x JS files using Google Closure templates. And for some reason, it simply does not like my arrow functions. For example:

// let showCurrentPage;
showCurrentPage = (i) => {
    currentPage = i;
    paginationCountLogic(bookMarksArray);
}

If I change to a different function type, for example:

    let showCurrentPage = function(i) {
        currentPage = i;
        paginationCountLogic(bookMarksArray);
    }

My function becomes usable or recognised in my JS file.

'showCurrentPage' is declared but its value is never read.ts(6133)

My code works fine, without compilation. And I have been googling for hours, but I can not seem to fix this.

I have even tried changing my NPM command, to compile from ES6 to ES5. But this does not seem to fixe the issue:

npx google-closure-compiler --js=app.js --js=pagination.js  --compilation_level ADVANCED_OPTIMIZATIONS --language_in ECMASCRIPT6  --language_out ECMASCRIPT5 --js_output_file=minified.js

Any ideas?

Here's the actual error:

pagination.js:43: ERROR - [JSC_UNDEFINED_VARIABLE] variable showCurrentPage is undeclared
    showCurrentPage = (i) => {
    ^^^^^^^^^^^^^^^

ANSWER

Answered 2019-Dec-17 at 18:47

I got this answered via another question. But this turns out to be the reason why:

The cause is probably that the compiler doesn't see the function being called. Part of the advanced compilation is removing unused code and renaming the methods/variables.

Within your js or html it is never called because the function call is only defined in a string value here :

for (var i = 0; i < individualPagesArray.length; i++) {
   document.getElementById("numbers").innerHTML += `<button onclick=showCurrentPage(${i+1})>` + individualPagesArray[i] + `</button>`;
}

you can solve this pretty simply by rewriting this:

window.showCurrentPage = (i) => {

to this:

window['showCurrentPage'] = (i) => {

See : https://developers.google.com/closure/compiler/docs/api-tutorial3#removal

Source https://stackoverflow.com/questions/59177109

QUESTION

strange object property behavior with closure compiler ADVANCED_OPTIMIZATIONS

Asked 2019-Dec-10 at 22:37

When running the following code compiled with ADVANCED_OPTIMIZATIONS, I get an unexpected output (for me at least).

/**
 * @typedef {{
 *      version: string,
 *      api_host: string
 * }}
 */
var AppProps;

/**
 * 
 * @param {AppProps} props 
 */
window['app'] = function(props) {
    props = props || {};
    console.log("props.api_host = ", props.api_host);
    console.log("props['api_host'] = ", props['api_host']);
};

Result:

props.api_host =  undefined 
props['api_host'] =  http://localhost:8080

Is this expected behavior for compiled object literals? Should I always be using string accessors for Object properties (something I almost never do)?

Any insight to this behavior will be greatly appreciated.

Cheers and thank you!

PS: closure-compiler version is v20191111, also the compiler has 0 knowledge of the object literal being passed in, with the exception of the @typedef. Function invocation happens outside of the compiled code.

PPS: Here is the rewritten code, which explains the output, but not the reasoning.

console.log("props.api_host \x3d ",a.B);
console.log("props['api_host'] \x3d ",a.api_host)

I would not expect closure-compiler to rewrite the first statement as it has, given the provided @typedef. What am I doing wrong here?

ANSWER

Answered 2019-Dec-10 at 22:37

After going through the docs and carefully considering my setup, I have found the errors of my ways, and a satisfactory explanation for the results.

Since everything within the compiled code, including my @typedef, is subject to rewriting, what I actually needed was an extern to describe the shape of this externally provided object.

externs.js

/**
 * @interface
 */
function AppProps() {}

/**
 * @type {string}
 */
AppProps.prototype.version;

/**
 * @type {string}
 */
AppProps.prototype.api_host;

app.js

/**
 * 
 * @param {AppProps} props 
 */
window['app'] = function(props) {
    props = props || {};
    console.log("props.api_host = ", props.api_host);
    console.log("props['api_host'] = ", props['api_host']);
};

The resulting output now works as expected.

Source https://stackoverflow.com/questions/59275017