Details

    • Type: Bug
    • Status: Open
    • Priority: None
    • Resolution: Unresolved
    • Affects Version/s: CLI Release 7.0.3
    • Fix Version/s: None
    • Component/s: CLI, Titanium
    • Labels:
      None
    • Environment:

      Ti SDK: 7.1.1.GA, 7.2.0.v20180528150435, 7.3.0.v20180530072516
      Node 10.3.0

    • Severity:
      Minor

      Description

      Description

      Node 10 produces a deprecation warning when the new Buffer constructor is used. See https://nodesource.com/blog/understanding-the-buffer-deprecation-in-node-js-10/ if you're curious

      In most cases I believe the most appropriate swap for us to do is turn new Buffer into Buffer.from

      There are a few instances in appc-cli-titaniums Titanium hook https://github.com/appcelerator/appc-cli-titanium/search?q=new+Buffer&unscoped_q=new+Buffer and none appear in appc-cli

      We might also wish to update eslint-config-axway to include the no-buffer-constructor rule

      Steps to reproduce to be added as replacement happens

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              eharris Ewan Harris
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Git Source Code