• Login
    • Report A Bug
    • System Information
    • System Tests
    • System Policies
    • Code Documentation
    • Occam Source Code
    • Web Client Source Code
    • About Occam
    • Acknowledgements
    • Guides / Documentation
    • Publications

translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
js-package
    estraverse5.3.0
    QmUkV3nLGo9HQV8AkSFR4Fdt6trRrVA19BonCgSGm51hQW
    5dsokhpviGs9ZcPyeh3CTg9WEVwcqY
      QmUkV3nLGo9HQV8AkSFR4Fdt6trRrVA19BonCgSGm51hQW
      5dsokhpviGs9ZcPyeh3CTg9WEVwcqY

      • Details
      • Files
      • History
        • Summary

          ECMAScript JS AST traversal functions

          Authors

            none

          Source

          https://registry.npmjs.org/estraverse

          Website

          https://github.com/estools/estraverse

          License

          • BSD-2-Clause

          Environment

          linux

          Architecture

          x86-64

          Versions

          • 5.3.0

          Related

          • maintainer

            npm

          ResourcesHelp

          This section tracks other objects or external resources.

          The external resources, such as tarballs or Git repositories, are then available as part of the object. Their files can be considered local to the object and usable in scripts or as part of a build process.

          For resources that are only to be used as part of the build or runtime of the object, it is best to describe those local to those sections.

          • estraverse-5.3.0.tgz7.86KiB

            application/gzip

            estraverse 5.3.0 Distribution

            https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz

            Qmcx9iGvyoWst1eN2SzktLpCfYYVRJkbSdAZxMfovay9y4

            QmXH4EqnvM6o3sgXh8sZfNCjcfhAQSHMCKucsXas5tYNBa

            QmSYpvrCcU5QdN7WhY4kpvqkD8Uf3FDMp31EnUFPXXbT3T

            download

          InstallationHelp

          Objects have a set of files that comprise that object, as seen in the Files tab. When an object is built, they have a set of files that are the result of that build. In each case, these sets of files are the ones that are accessible within a virtual machine when running the object.

          This section describes how those files are accessible and visible to that machine. When a virtual machine is created, the data is always accessible read-only within a particular mounted directory. However, applications may expect to be located at particular directories. This section allows one to place files in different directories when the virtual machine is launched.

          There are two types of access. One is a link where the file is not copied from its original location. Instead, it creates what is called a symbolic link which is a "shortcut" that acts like a normal file but allows the actual data to be in a different directory. The other type is a traditional copy which copies the data explicitly to the provided destination. This takes more time, but the copy can be modified, unlike the read-only link type.

          ActionSourceDestinationSummary
          Copyestraverse-5.3.0.tgz/opt/npm/cache/_cacache/content-v2/sha512/30/c7/4046e54443388d4de243f0380caa6870475d41450fdc04ffa92ed61d4939dfdcc20ef1f15e8883446d7dfa65d3657d4ffb03d7f7814c38f41de842cbf004

          N/A

          No files will be installed.

          Share

          • URL

            Copy
          • Embed Link

            Copy
          • QR Code

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        Confirm
        Do you wish to proceed?

        Confirm message?