Skip to content

Question: Populating the streamline cache with _node -c / detecting existing already-transpiled code during require() #384

@Maciek416

Description

@Maciek416

Some questions about transpilation and caching:

Given both of the following cases:

  • require("xyz/abc._js")
  • require("xyz/abc")

Does streamline first check to see if a transpiled version, i.e. xyz/abc.js, already exists before attempting to load or transpile the ._js version? In other words, does running through the _node -c <filename> for every file in my codebase effectively "warm up the streamline cache"?

Alternatively, is there a way to "warm up" streamline's own transpilation cache using _node -c or a similar process?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions