Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

src directory missing from NPM registry package

See original GitHub issue

When trying to create a new project using the @glimmer/blueprint:

ember new hello-glimmer -b @glimmer/blueprint

The new glimmer project seems to be missing the src directory. Looking directly at the npm registry entry:

▶ npm view @glimmer/blueprint

@glimmer/blueprint@1.0.0 | MIT | deps: 1 | versions: 58
Ember CLI blueprint for initializing a new Glimmer application.
https://github.com/glimmerjs/glimmer-blueprint#readme

keywords: ember-blueprint, ember-addon

dist
.tarball: https://registry.npmjs.org/@glimmer/blueprint/-/blueprint-1.0.0.tgz
.shasum: 9d079be8cf38a5c4c526dce93882e3484bf93543
.integrity: sha512-hnbH5VeoDy36mgP4C+utiThZYz+WJeICHAaouYUguNFaAPpEcJWTRQplqrTYoWkJxKF6+6FIIjNFc+aZbSBi7Q==
.unpackedSize: 10.5 kB

Downloading the tarball at https://registry.npmjs.org/@glimmer/blueprint/-/blueprint-1.0.0.tgz, the src directory is missing from /files.

Issue Analytics

State:
Created 4 years ago
Reactions:13
Comments:6 (1 by maintainers)

Top GitHub Comments

5reactions

jsDeveloper98commented, Dec 24, 2019

use this version of blueprint ember new my-app -b @glimmer/blueprint @0.13.0

2reactions

pzuraqcommented, Feb 27, 2020

We are currently working on v2 of Glimmer.js, which will have a very different build pipeline based primarily on Webpack (with a standard setup generated via ember-cli). Stay tuned!