Skip to content

Packaging and module loading questions #117

@wyattanderson

Description

@wyattanderson

Hey, I have a couple quick questions about packaging and module loading of Orbit.js:

  1. What's the preferred way to load Orbit.js? CommonJS support with the version distributed on Bower seems lacking. If I require orbit-common and orbit-common-jsonapi, Orbit and OC are actually leaked to the window object. Is this intentional? Is there a way to build Orbit to avoid this? Are ES6 modules preferred?
  2. Why isn't Orbit published to NPM?

I'm trying to set up a new project with Orbit in a CommonJS/webpack stack and these two things are making it tough.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions