How can I out the latest available version of a specified pod? For example, FirebaseRemoteConfig?
You can run the command pod search PodName in the terminal and it will list all of the available versions in descending order. The latest version will appear first.
pod search FirebaseRemoteConfig presently shows 10.3.0 as the latest.
Related
I have a local pod that has to use an older version of the OpenSSL framework. My main project uses this local pod and a newer version of the OpenSSL framework. This creates ambiguous use inside code. My question is if it is possible to make this older version reachable only from my local pod, but not from other pods or the main project file?
Only by renaming all of the symbols in one of them. See https://github.com/google/boringssl for an example of this.
Using the latest nativescript core w/ Android 6.5
In the project file, I see I'm using nativescript-theme 2.2.1
I see the latest version is 2.3.4.
I do npm outdated on the command line and nativescript-theme is not listed.
Anyone know why I cannot update to the latest version?
I also did npm outdated #nativescript/theme.
I've just downloaded the latest Nativescript Sidekick. When I try to run it, I get the message that it is expecting:
"NodeJS >=8.0.0 <=10.5.0"
I'm using nvm, so I can switch node versions at will, but Sidekick appears to ignore this and pick up the latest (10.9.0 in my case). How does Sidekick detect the nodejs version? And how can I persuade otherwise???
After #GGarabedian confirmed that it worked with NVM for him, I played around a bit and discovered that Sidekick is looking for the NVM alias Stable.
So, by setting the alias to v8.11.0, Sidekick did work for me.
nvm alias stable v8.11.0
I have tested NativeScript Sidekick with the Node Version Manager and it appears to detect the currently selected Node version correctly. Can you verify if you have installed and selected a NodeJS version between 8.0.0 and 10.5.0 by running the node --version command in the Command Prompt?
Also, my tests were conducted on a Windows machine and it would be good to know if you are running on the same or different OS.
Is there a legacy mode for Cocoapods that allows a user to use a version of Cocoapods as if it was an older one? Eg use 1.0.0 as if it was 0.39 via a command line argument to avoid downloading legacy versions.
You will need the version to be installed. However, there is nothing wrong with having multiple versions installed. You can also delete them if you no longer need a specific version.
Once installed, run the version you want with this:
pod _0.39.0_ YourCommandHere
Change the version number as needed.
I've installed amnah/yii2-user library from packagist via composer into my project. The project's composer.json relevant require section looks like:
"amnah/yii2-user": "~2.0"
To my understanding, this should install the latest version with a major version of "2". When I check the installed package via composer show amnah/yii2-user -v, I see the following version information:
versions : dev-master, 2.1.0-alpha4, 2.1.0-alpha3, 2.1.0-alpha2, 2.1.0alpha,
* 2.0.0-alpha2, 2.0.0-alpha, 1.0.0-beta
So 2.0.0-alpha2 is installed, the 2.1 versions are ignored. Isn't it supposed to work like
Another way of looking at it is that using ~ specifies a minimum
version, but allows the last digit specified to go up.
as the documentation states? I'd need the latest 2.x version installed. What am I missing?
If you need the latest 2.x version installed, you should use ~2.1 if "latest" means that at that time a version 2.1 is the most current version released.
But I wonder why you are getting the alpha version installed. Usually Composer defaults to only install stable versions, no release candidates (rc), beta, alpha nor dev versions. Did you add a setting for minimum-stability and/or preferred-stability?
So if you want alpha versions, you should require ~2.1#alpha.
And a word of caution: The project you are using does require yiisoft/yii2: * and yiisoft/yii2-authclient: * - asterisk meaning that ANY version is sufficient. Yii itself claims that the released 1.1 version is incompatible with the newer 2.0 series (which is not yet released), whatever that means.