require and import

[paxperscientiam]

There's a note in the readme indicating that noLib is fixed at false. Does that mean ts2gas does not currently handle imports? Like, I'm trying to import a module, but nothing seems to happen.

Thanks.

[grant]

ES Modules aren't supported in this library. (for require and import)
I think some developers have their own webpack setup for TypeScript compilation.

• https://github.com/naoki-sawada/gas-typescript-webpack
• https://stackoverflow.com/questions/48791868/use-typescript-with-google-apps-script

noLib just removes things like window, document from autocompletion.

• https://basarat.gitbooks.io/typescript/docs/types/lib.d.ts.html
• https://www.typescriptlang.org/docs/handbook/compiler-options.html

[angrykoala]

import is not supported and it is commented out by ts2gas, however export is actually transpiled into exports.foo=foo, this completely breaks the compiled appscript, as foo is not part of the global scope and imports are simply commented out.

Is there a way to disable this behavior, so both import and export are simply commented out?

[grant]

@paxperscientiam @angrykoala Can you provide some test cases so we can test and fix this?

@PopGoesTheWza has written most of this library, so you may want to check up on the case with him/her.

[angrykoala]

export default const myFoo="foo";

my_foo.ts

import myFoo from './my_foo.ts';

console.log(myFoo)

main.ts

This should transpile to valid Appscript, preferably by overriding export/import (a lá browserify) but at the very least should completely ignore export and import:

var myFoo="foo";

my_foo.gs

console.log(myFoo)

main.gs

I hope these examples help

[PopGoesTheWza]

@angrykoala please specify your build/publish workflow. Currently ts2gas is not designed to transpile more than one source .ts file at a time.

With my (little and very personal) use of clasp/ts2gas, I hardly had to mess with export and `import:

• I use export in the source code of GAS libraries (with its .d.ts)
• I adapt the library `.d.ts' file to be "this is a gas library" friendly (this is something I should look into automating probably)
• I use 'import' in the script consuming the library referencing the .d.ts

Unless @grant decides a different design approach, in which import should be handled (I am not sure yet of a satisfying option...)

[angrykoala]

the problem I have is that export is being transpiled instead of ignored, so I need to manually remove the generated code. Simply ignoring it (like it happens with import) would be enough and will work on transpiling one file at a time

[PopGoesTheWza]

@paxperscientiam please bear with my slowmindedness...

Checking at the result of ts2gastest suite:

v--TS--v
// next statement will be ignored
export { foo, bar }
  from "file";
// next statement will be preserved
/** Supported languages for localized data */
export enum Languages {
  /** English (USA) */
  eng_us = 'eng_us',
  /** French (France) */
  fre_fr = 'fre_fr',
}
export class Client {
  /** URL to the login endpoint */
  private readonly signinUrl: string;
}
export function foo() {}
export default Client;
export
  { ZipCodeValidator };
// now resume with next statement
–––
// Compiled using ts2gas 1.6.0 (TypeScript 3.3.3333)
var exports = exports || {};
var module = module || { exports: exports };
//export { foo, bar }\n  from "file";
// next statement will be preserved
/** Supported languages for localized data */
var Languages;
(function (Languages) {
    /** English (USA) */
    Languages["eng_us"] = "eng_us";
    /** French (France) */
    Languages["fre_fr"] = "fre_fr";
})(Languages = Languages || (Languages = {}));
var Client = /** @class */ (function () {
    function Client() {
    }
    return Client;
}());
exports.Client = Client;
function foo() { }
exports.foo = foo;
// now resume with next statement
 ^--GS--^

Most export statements are removed or ignored during transpiling. Classes, functions and variables end up producing the following:

exports.Client = Client;
exports.foo = foo;

Are those the lines you wish would not be produced? What is the impact of those lines being in your gas?

[PopGoesTheWza]

incidentally, I now wonder why export enum Languages ... produces an incorrect (Languages = Languages || (Languages = {}))
The correct resulting javascript should read (Languages = exports.Languages || (exports.Languages = {}))

@grant I'll investigate this sometime this week.

[angrykoala]

@PopGoesTheWza Yep, those are the things that I would like to ignore (thanks, sorry for not explaining myself, it was quite some time ago since I had this problem), unless import actually access the "export" global variable" it is impossible for the code to reach these variables

thanks

[PopGoesTheWza]

@angrykoala I failed to see the use of export (for classes, functions, enums and variables) unless when producing a gas library. Does this match your use case?

If you are solely producing "alongside .gs scripts", they all exist in the same global namespace:
Code.gs

foo()

lib.gs

function foo() {
  return 'zug zug';
}

Is there something obvious I am overlooking?

[angrykoala]

lets assume 2 files in ts:

export default class Foo{ }

import Foo from 'foo'
new Foo()

It will transpile to:

exports.Foo=class Foo ....

new Foo()

As you can see, the Foo in the second file won't be found because Foo is not in the global scope, but in the object exports.

[PopGoesTheWza]

@angrykoala are you using clasp to publish your two files? If you have src1.ts and src2.ts, doesn't it ends up as src1.gs and src2.gs in your gas document?

[angrykoala]

Yes, that's correct,but the class Foo won't be found in src2.gs because it is not declared in the global scope of src1.gs, but as part of the exports object

[PopGoesTheWza]

@angrykoala odd... for this does not match my (limited) experience. Maybe it is related to my project settings, but when pushing src1.ts and src2.ts, I get in my gas project src1.gs and src2.gs which share the same global namespace... hence src1.gs call functions from src2.gs as if they were alongside in a single file.
To illustrate, you may give a look at https://github.com/PopGoesTheWza/swgoh-tb-sheets which has some limited import to access a gas library (using lib/index.d.ts for type definitions) and all other scripts sharing the same global namespace (hence no need for import/export
@grant could you share some of your wisdow here?