Skip to content

It's difficult to use a berg.scheduler.workerProxy because of file path issues #28

@colinbdclark

Description

@colinbdclark

Currently, the berg.scheduler.workerProxy requires a separate JavaScript file to be loaded into the worker (which includes Infusion and everything else needed by Bergson). When consuming Bergson as an npm module and using its dist/bergson-only.js file, the worker's JavaScript file is not found, and a user has to override this value (which is difficult in the case where the client of Bergson is itself a framework).

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