-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to repackage Angular2 packages on Atmosphere #1211
Comments
@hongbo-miao please read this chapter of the tutorial and let me know if that worked for you - http://www.angular-meteor.com/tutorials/socially/angular1/3rd-party-libraries |
@Urigo thx for link, I will read it |
my bad seems solution #1 is what we need |
@Urigo Sorry, I failed after some tries... I think it needs put some d.ts files in typings automatically after downloading the package, but I don't know how to create those files. How about creating a tutorial Step |
Hi, I also tried to package angular2-materialize package for Meteor, but failed. Main problem so far is packing any .ts files for Meteor, as well as packing npm dependencies of the original package that don't already exist on Atmosphere. |
@hongbo-miao I kinda succeeded to transpile TS and package it for meteor using the package.js like in https://github.com/barbatus/ng2-meteor-accounts/blob/master/package.js |
@valorkin @MilosStanic I got help from zrbfly, who first succeed packaging ng2-bootstrap, I will let you know details of how to package it once I am clear those steps. |
with the new Meteor version you can just use npm and import styles from it |
Oh, yeah, it is working well now using NPM. |
Hi, @Urigo and everyone, can you give us, especially the author of ng2-bootstrap, ng2-charts, ng2-file-upload @valorkin some directions for repackaging these Angular2 style packages on Atmosphere to let them be reused in the future angular2-meteor project?
@valorkin's packages are really high-quality style packages for angular2. All their packages can be found here.
valor-software/ng2-file-upload#49
The text was updated successfully, but these errors were encountered: