Ivan igodorogea

## angular-cli-node-js-typescript-rxjs-compatiblity-matrix.csv

          
            Angular CLI version
            Angular version
            Node.js version
            TypeScript version
            RxJS version

            
              ~16.0.0
              ~16.0.0
              ^16.13.0 || ^18.10.0
              	>=4.9.5 <5.1.0
              ^6.5.5 || ^7.4.0

            
              ~15.2.0
              ~15.2.0
              ^14.20.0 || ^16.13.0 || ^18.10.0
              	>=4.8.4 <5.0.0
              ^6.5.5 || ^7.4.0

            
              ~15.1.0
              ~15.1.0
              ^14.20.0 || ^16.13.0 || ^18.10.0
              	>=4.8.4 <5.0.0
              ^6.5.5 || ^7.4.0

            
              ~15.0.5
              ~15.0.4
              ^14.20.0 || ^16.13.0 || ^18.10.0
              	~4.8.4
              ^6.5.5 || ^7.4.0

            
              ~14.3.0
              ~14.3.0
              ^14.15.0 || ^16.10.0
              	>=4.6.4 <4.9.0
              ^6.5.5 || ^7.4.0

            
              ~14.2.0
              ~14.2.0
              ^14.15.0 || ^16.10.0
              	>=4.6.4 <4.9.0
              ^6.5.5 || ^7.4.0

            
              ~14.1.3
              ~14.1.3
              ^14.15.0 || ^16.10.0
              	>=4.6.4 <4.8.0
              ^6.5.5 || ^7.4.0

            
              ~14.0.7
              ~14.0.7
              ^14.15.0 || ^16.10.0
              	>=4.6.4 <4.8.0
              ^6.5.5 || ^7.4.0

            
              ~13.3.0
              ~13.3.0
              ^12.20.2 || ^14.15.0 || ^16.10.0
              >=4.4.4 <4.7.0
              ^6.5.5 || ^7.4.0

## Vagrantfile
# If you are using Windows as your Vagrant host OS, there is a limitation in Windows where any given folder path
# cannot be more than 260 characters long. This becomes a problem with Vagrant because, for example, if you
# install a Linux guest environment and try to create a deep directory structure in a synced folder, Linux will
# throw errors. This is because the synced folder is under the constraints of the Windows host. A common example
# of this happening is when installing node.js modules. NPM is known for creating some very long, deep
# folder paths because each node depenency has it's own dependencies, which have their own dependencies, etc...
#
# This gist solves the problem and works around the Windows 260 character path limit. Add it to your Vagrantfile.
#
# NOTE: This bug in Vagrant was fixed in 1.7.3, but reverted back in 1.7.4 due to some regression bugs.

## gist:598fa75e22bdfa44cf47

      
              1 file
            
          
              61 forks
            
          
              61 comments
            
          
              995 stars
            
          
                wincent
                / gist:598fa75e22bdfa44cf47
            
            
              Last active
              April 2, 2024 18:21
            
          
2015-01-29 Unofficial Relay FAQ

Compilation of questions and answers about Relay from React.js Conf.

Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.


What is Relay?


Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).
  

## ubuntu-compass-ruby
#https://gorails.com/setup/ubuntu/14.04
sudo apt-get update
sudo apt-get install git-core curl zlib1g-dev build-essential libssl-dev libreadline-dev libyaml-dev libsqlite3-dev sqlite3 libxml2-dev libxslt1-dev libcurl4-openssl-dev python-software-properties
sudo apt-get install libgdbm-dev libncurses5-dev automake libtool bison libffi-dev

curl -L https://get.rvm.io | bash -s stable
source ~/.rvm/scripts/rvm
echo "source ~/.rvm/scripts/rvm" >> ~/.bashrc
rvm install 2.1.2
rvm use 2.1.2 --default
Angular CLI version	Angular version	Node.js version	TypeScript version	RxJS version
~16.0.0	~16.0.0	^16.13.0 \|\| ^18.10.0	>=4.9.5 <5.1.0	^6.5.5 \|\| ^7.4.0
~15.2.0	~15.2.0	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	>=4.8.4 <5.0.0	^6.5.5 \|\| ^7.4.0
~15.1.0	~15.1.0	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	>=4.8.4 <5.0.0	^6.5.5 \|\| ^7.4.0
~15.0.5	~15.0.4	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	~4.8.4	^6.5.5 \|\| ^7.4.0
~14.3.0	~14.3.0	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.9.0	^6.5.5 \|\| ^7.4.0
~14.2.0	~14.2.0	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.9.0	^6.5.5 \|\| ^7.4.0
~14.1.3	~14.1.3	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.8.0	^6.5.5 \|\| ^7.4.0
~14.0.7	~14.0.7	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.8.0	^6.5.5 \|\| ^7.4.0
~13.3.0	~13.3.0	^12.20.2 \|\| ^14.15.0 \|\| ^16.10.0	>=4.4.4 <4.7.0	^6.5.5 \|\| ^7.4.0
	# If you are using Windows as your Vagrant host OS, there is a limitation in Windows where any given folder path
	# cannot be more than 260 characters long. This becomes a problem with Vagrant because, for example, if you
	# install a Linux guest environment and try to create a deep directory structure in a synced folder, Linux will
	# throw errors. This is because the synced folder is under the constraints of the Windows host. A common example
	# of this happening is when installing node.js modules. NPM is known for creating some very long, deep
	# folder paths because each node depenency has it's own dependencies, which have their own dependencies, etc...
	#
	# This gist solves the problem and works around the Windows 260 character path limit. Add it to your Vagrantfile.
	#
	# NOTE: This bug in Vagrant was fixed in 1.7.3, but reverted back in 1.7.4 due to some regression bugs.
	#https://gorails.com/setup/ubuntu/14.04
	sudo apt-get update
	sudo apt-get install git-core curl zlib1g-dev build-essential libssl-dev libreadline-dev libyaml-dev libsqlite3-dev sqlite3 libxml2-dev libxslt1-dev libcurl4-openssl-dev python-software-properties
	sudo apt-get install libgdbm-dev libncurses5-dev automake libtool bison libffi-dev

	curl -L https://get.rvm.io \| bash -s stable
	source ~/.rvm/scripts/rvm
	echo "source ~/.rvm/scripts/rvm" >> ~/.bashrc
	rvm install 2.1.2
	rvm use 2.1.2 --default