Package types

Previously you learned how to start using Eik in an application, including how to do import mapping so shared dependencies only get downloaded, parsed and run once. For this to work, though, there must be shared dependencies available on the Eik server.

In the Managing dependencies section you'll learn how to:

• publish shared dependencies to the npm namespace on your Eik server
• how to create and publish import maps to your Eik server
• how to create aliases for both of the above

Eik package types

It's worth mentioning at this stage that Eik differentiates between these types of packages:

• npm
• map
• package
• image

You'll see this distinction in eik.json and in the URL where your package gets published. Each package type has its own namespace. This is to avoid accidental naming collisions between, say, the npm module lit and the import map lit.

Application code should be published to the package namespace. This is also the default, if no other type is configured in eik.json.

Long-lived static assets like images should be in an image package, separate from frequently-changing application code.

Naming and versioning packages

Packages published to Eik should follow the npm module naming convention and Semantic Versioning. This applies to all namespaces, although semantic versioning is less relevant for application code.

Next steps

Let's learn how to publish a package to the npm namespace on Eik.