adopted-ember-addons / adopted-ember-addons/ember-paper
package.json gitclone
- 主要言語
- JavaScript
- スター
- 879
- フォーク
- 327
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
Hi,
I'm not sure if this is the correct place to post this but here goes:
We currently use ember-paper 0.2 and are looking to upgrade to 1.0 for its new features. We are behind a firewall that we can't poke holes through, so we have our own sonartype nexus repository that we load npm modules into. npm is setup to use this repo and it works fine for most cases.
However, with the latest ember-paper 1.0 releases, there's a package for angular material defined like so:
`"angular-material-source": "github:angular/material#v1.1.4",`
This runs a git clone command under the covers which is breaking our builds when running npm install as it doesn't have access to github in order to download angular-material-source.
I don't quite understand why this is done this way as I'm not that familiar with it, but can this be pulled into ember-paper as a normal npm dependency instead without using the github url format?
コントリビューションガイド
評価
この issue はまだ評価されていません。