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.
Nightly builds @angular2-material/XXXX@next
See original GitHub issueBug, feature request, or proposal: feature/proposal
What is the expected behavior?
Provide nightly builds reflecting master in NPM
What is the current behavior?
No nightly builds.
What is the use-case or motivation for changing an existing behavior?
Currently there are a lot of things evolving, sometimes a feature exists in master for a while until it is released. One can “compile” his own version with little effort but this mean hassle for the project, either npm link the clone or removing the material dependencies from package.json and loosing the npm dependency inspection
Having @angular2-material/core@next will ease up the process.
Which versions of Angular, Material, OS, browsers are affected?
None
Issue Analytics
- State:
- Created 7 years ago
- Reactions:15
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We publish all of our builds to git repos instead (example). you can install them from there via:
I prefer git repos because they allow us to publish artifacts after each commit without flooding the npm. Additionally, it’s easy to review what’s being published and see the diffs as well we remove old version whenever we want to (unpublishing from npm is tricky and sometimes impossible).
@Chris1308 that build was broken. This will happen when installing from master- that’s why we do releases 😃