Skip to content
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 should I use the newest three.dart #190

Open
Jiakui opened this issue Mar 11, 2015 · 4 comments
Open

How should I use the newest three.dart #190

Jiakui opened this issue Mar 11, 2015 · 4 comments

Comments

@Jiakui
Copy link

Jiakui commented Mar 11, 2015

I saw that on Dart Pub the three.dart package is pretty outdated [https://pub.dartlang.org/packages/three]. How should I used the newest three.dart in my project?

Thanks!

@bgourlie
Copy link

You can specify a git repository as a pub dependency. It's not ideal, but
it's the only choice we have right now for three.dart. See
https://www.dartlang.org/tools/pub/dependencies.html

On Wed, Mar 11, 2015 at 11:21 AM, Jiakui [email protected] wrote:

I saw that on Dart Pub the three.dart package is pretty outdated [
https://pub.dartlang.org/packages/three]. How should I used the newest
three.dart in my project?

Thanks!


Reply to this email directly or view it on GitHub
#190.

@cgrabowski
Copy link
Contributor

Furthermore, you can prevent merges into master from potentially breaking your code by forking the three.dart git repository and then listing your copy of the repository as the dependency in your pubspec.yaml. If you do it that way you can wait to pull merges from the main repository until you are ready to deal with any problems it causes in your projects that depend on three.dart.

@bgourlie
Copy link

Alternatively, you can peg a particular commit right in the pubspec.

On Wednesday, March 11, 2015, Christopher Grabowski <
[email protected]> wrote:

Furthermore, you can prevent merges into master from potentially breaking
your code by forking the three.dart git repository and then listing your
copy of the repository as the dependency in your pubspec.yaml. If you do it
that way you can wait to pull merges from the main repository until you are
ready to deal with any problems it causes in your projects that depend on
three.dart.


Reply to this email directly or view it on GitHub
#190 (comment)
.

@cgrabowski
Copy link
Contributor

Oh cool! I didn't know that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants