npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ember-engines-microservice

v0.1.0

Published

The default blueprint for ember-cli addons.

Downloads

6

Readme

ember-engines-microservice

Deploy standalone lazy-loading engines without having to deploy from main ember application for every little changes.

Installation

  • ember install ember-engines-microservice

Usage

Instead of asset manifests injected into the meta tag, it will create dist/engines-dist/engine-name/asset-manifest.js file with all the uri to engines asset.

  • ember serve
  • ember deploy
  • ember build

Prerequisite

Ember App and Ember Engine

  • ember-cli-deploy

Ember Engine

  • Must have the same filterprint option in ember-cli-build.js as the main ember app the engine is mounting to
  • Must have the same config/deploy.js configuration as the main ember app the engine is mounting to

Configuration

Ember Engine

Add isEngine: true in ember-cli-build.js

var app = new EmberAddon(defaults, {
  isEngine: true
});

Ember App

Add below snippet in app/index.html

{{content-for "engine-assets"}}

under

<script src="{{rootURL}}assets/vendor.js"></script>

Example app/index.html:

<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <title>Dummy</title>
    <meta name="description" content="">
    <meta name="viewport" content="width=device-width, initial-scale=1">

    {{content-for "head"}}

    <link rel="stylesheet" href="{{rootURL}}assets/vendor.css">
    <link rel="stylesheet" href="{{rootURL}}assets/dummy.css">

    {{content-for "head-footer"}}
  </head>
  <body>
    {{content-for "body"}}

    <script src="{{rootURL}}assets/vendor.js"></script>
    {{content-for "engine-assets"}}
    <script src="{{rootURL}}assets/dummy.js"></script>

    {{content-for "body-footer"}}
  </body>
</html>

Running Tests

  • npm test (Runs ember try:each to test your addon against multiple Ember versions)
  • ember test
  • ember test --server