| # Scale workers on Heroku automatically as your Resque queue grows. | |
| # Mixin the +Scaling+ module into your models to get the behavior. | |
| # | |
| # class MyModel < ActiveRecord::Base | |
| # extend HerokuAutoScaler::AutoScaling | |
| # end | |
| # | |
| # And configure in an initializer +config/initializers/heroku_workers.rb+: | |
| # | |
| # HerokuAutoScaler.configure do |
| #import "RCTEventEmitter.h" | |
| #import "RCTBridge.h" | |
| @interface GSEventEmitter : RCTEventEmitter <RCTBridgeModule> | |
| + (BOOL)application:(UIApplication *)application didSightBeacon:(NSString *)beaconID; | |
| + (BOOL)application:(UIApplication *)application didDepartBeacon:(NSString *)beaconID; | |
| @end |
| class City < GeoEntity | |
| def self.sti_name | |
| 3 | |
| end | |
| end |
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
This solution fixes the error caused by trying to run npm update npm -g. Once you're finished, you also won't need to use sudo to install npm modules globally.
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.