How to customize a Bower package locally? - ruby-on-rails

So if i’m using a Bower package (specifically, this one: https://github.com/DmitryBaranovskiy/raphael/ ) and there’s a tiny bug in it. It’s not really a big deal, and there’s a PR for it: https://github.com/DmitryBaranovskiy/raphael/pull/645 but it seems like the PR won't be merged anytime soon... Is there a way to incorporate this fix into (at least) my local version of the package without theoretically losing all the Bower-goodness? I’m a Bower newbie. I guess I’m asking is there a way to ‘customize’ a Bower package?
(For context, I’m using Bower hooked into the Rails asset pipeline as described here: http://dotwell.io/taking-advantage-of-bower-in-your-rails-4-app/ )
Thanks!

I feel your pain in regards to pull-requested patches :) Unfortunately, there's not really a clean way to do this.
One way to do this would be to:
Fork Raphel
Incorporate the fix you need
Update your bower.json to point raphel to your personal github fork"raphael": "yourusername/rapheal#branch_name"
Switch back to the "cannonical" raphel once the fix is merged
Edit
My original answer was given without realizing the original PR was 3 years old. I've updated to advocate for forking Raphel.

Related

How to upgrade NuGet packages without breaking my project?

I have an old MVC application I need to make changes to. It would be nice to update all the recommended NuGet packages, but I know from experience that this can break a project.
In particular, I'm troubled by the following:
If one reads this a certain way, it appears that it's actually suggesting I upgrade to Twitter Bootstrap 5.1.2. I know for a fact that numerous breaking changes have been implemented since my current version.
I prefer not to have to rewrite the site. I thought Updates might have been a little smarter. Do I really need to know each package well enough to know if it would include breaking changes? Is there no way to specify compatible updates? Did Microsoft consider this aspect?
You do need to know each package well enough. Why? Because there's not a single way of doing versioning. Some packages, probably a lot of packages even, follow Semantic Versioning, but there's nothing to stop anyone from using any versioning they want (even if it doesn't make sense). There's nothing preventing you from going 3.0.1 to 15.14.13 with a change in an unimportant .txt file.
It's your responsibility to know what to update and when. Look at this Q&A to see how you can restrict the versions suggested: NuGet Limit max major version of a package

Purescript - Unable to build with drawing and signals libraries

I'm trying to start a purescript project that uses the purescript signal and drawing libraries. When I try to bower install with both of them as dependencies, bower's interactive prompt asks to resolve several dependency versions. I admittedly pick the versions somewhat arbitrarily since most of the issues are several layers of dependencies deep. Then when I pulp build a basic hello world piece of code that doesn't even use the dependencies, pulp gives around 40 errors depending on which versions I selected.
How do I resolve these dependency versions correctly? Sifting through forty errors and all of the dependencies for both projects doesn't seem feasible. Is there some non-arbitrary way of picking the versions that will resolve the conflicts? From the choices it gave me, it didn't seem like there was any clear resolution. Or are their dependencies too conflicting and you just can't use them together?
This may actually be more of an question about bower, but it may also be something about purescript and pulp that I am just unaware of. They both seem like libraries that should be able to work together, and I can't imagine that other people are having too much difficulty using two or more libraries in a single project.
Purescript 0.10 has breaking changes. If you have the latest compiler, it's likely that it's not compatible with some libraries. From what I see, signal lib is updated but the drawing is not. You can update the lib and use your own version. Or, send a PR, Phil and purescript community in general, is really fast on responding to pull requests.
Another temporary solution is to use the old compiler (0.9) and wait a couple months till everything is back to normal.
also see 0.10 migration guide.

is it possible to use different core library version for testing rails

I love OSS contribution but trying to get involved into OSS contribution. Recent I give a try to rails 4.2.4.rc1 with rails 4.2.3 and got failure for testcases.
The app works perfectly with rails4.2.3 and in the latest release candidate it's throwing some errors. I'm trying to figure out the issue.
could anyone help me to find the change from 4.2.3 version to 4.2.4.rc1 in main rails repository? I feel that will help me to resolve the bug.
How I can find the difference from github.
Note: changeLog only contains the error message not the commit details.
I am not sure that I grasp your question.
You are speaking about tests from rails but also about an app that works.
If you want to try different rails versions for your app, I would use rvm and gemsets. Official documentation, but you will find imho nicer tutorials about that elsewehere. Actually, I would always use rvm and gemsets :) .
Changes between two versions can be seen on the github webpages, e.g. for rails - coming from the small green two-arrow-button to create pull-requests. Or you do it on the commandline git help diff, plus there are various graphical tools which I rarely resort to use (I am happy with gitk but there are probably fancier alternatives).

Is there anywhere I can get (relatively new) stable versions of Dart?

So I upgraded to 1.4 for a project I am contributing to (in development/testing branch of course) and ran into some problems and thus we want to use Dart 1.3.6 again. However, I cannot find this.
Does anyone know where I could download it?
I have seen and starred https://code.google.com/p/dart/issues/detail?id=18323
as I was putting this question together, but of course seems like there is no more movement there just yet.
I think I pretty much ran into similar issues to what corgath described in comments on this question... looking for the right version in those "archives" where the "latest" is not really the latest anymore.
Update
There is now a nice page to select and download specific Dart versions https://www.dartlang.org/tools/download-archive/
Since a while there are also deb packages available which can be installed using
sudo apt-get install dart=1.7.0-dev.0.1.*
see https://www.dartlang.org/tools/debian.html for more details.
Original
You can download from
http://gsdview.appspot.com/dart-archive/channels/stable/release/
The list only contains the build number but each folder contains a file VERSION that contains detailed version information for this build.
dev channel releases can be found here
http://gsdview.appspot.com/dart-archive/channels/dev/release/
there are also unsigned raw builds (bleeding edge) but it is not recommended to use them.
http://gsdview.appspot.com/dart-archive/channels/be/raw/release/

Is there a working solution for integrating Neo4j 1.6 in NodeJS?

I have found some relevant modules on Github but they do not work.
Does anyone know of some other available solutions?
Those are the three I have tried:
https://github.com/bobby/node-neo4j
https://github.com/gasi/node-neo4j
https://github.com/neo4j/neo4js
Go with the repo made by the people who make Neo4J: https://github.com/neo4j/neo4js
Like I mentioned, it is created and maintained by the people behind Neo4J and is constantly updated. I am using this currently in a project and it works fantastically well. Only thing to know is that you need to be running Node.JS 1.6 or better for the modules to work.
If you have any questions drop me a line or you can also ask in their discussion forum here: http://neo4j.org/nabble/
I'm one of the authors/maintainers of #gasi's node-neo4j (npm install neo4j). We have admittedly not upgraded it for 1.6 (we're still on 1.4 here but plan on upgrading soon), but it works entirely well -- we've been using it on our production site for many months now!
Can I ask what the issue is? Btw, we moved the repo to our formal organization's repo: https://github.com/thingdom/node-neo4j
Take a look at: https://github.com/philippkueng/node-neo4j
npm install node-neo4j
We're currently working on an upgrade to Neo4j 2.0.
It will support insert node with label, indexes on labels, CRUD for labels, constraints and streaming.
My work in progress (fork): https://github.com/Stofkn/node-neo4j

Resources