[dev] main.js built from Linux different than one built from Windows

Open
#220 0 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

backlog bug dependencies

The final output is the same size but the order of the exports has one difference. No breaking functionality as the order doesn't matter during runtime, but breaks our check-lib workflow.

This is the block that is different:

2609: function(e, t, n) {
    "use strict";
    var i = this && this.__awaiter || function(e, t, n, i) {
        return new(n || (n = Promise))((function(r, o) {
            function s(e) {
                try {
                    c(i.next(e))
                } catch (e) {
                    o(e)
                }
            }

            function a(e) {
                try {
                    c(i.throw(e))
                } catch (e) {
                    o(e)
                }
            }

            function c(e) {
                var t;
                e.done ? r(e.value) : (t = e.value, t instanceof n ? t : new n((function(e) {
                    e(t)
                }))).then(s, a)
            }
            c((i = i.apply(e, t || [])).next())
        }))
    };
    Object.defineProperty(t, "__esModule", {
        value: !0
    });
    const r = n(2225),
        o = n(4458);
    t.AuthorizerFactory = class {
        static getAuthorizer() {
            return i(this, void 0, void 0, (function*() {
                r.debug("try-get AzureCLIAuthorizer");
                try {
                    return yield o.AzureCLIAuthorizer.getAuthorizer()
                } catch (e) {
                    throw r.debug(e), new Error("No credentails found. Add an Azure login script before this action.")
                }
            }))
        }
    }
},
Dominant language
TypeScript
Stars
142
Forks
73
Avg merge
9d 18h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/sql-action

All issues in Azure/sql-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.