Gvsharma patch 2 (#33242)
* Updated index Added Kotlin resources * Update index.md spell mistakes corrected
This commit is contained in:
committed by
Christopher McCormack
parent
9c54ca8ee3
commit
b9d8bf9697
@ -64,6 +64,8 @@ Kotlin was developed by JetBrains, the company behind one of the most popular Ja
|
||||
|
||||
Because Kotlin generates Java bytecode, you can use your favorite Java frameworks and libraries in Kotlin and your Java friends can also use any Kotlin framework you develop.
|
||||
|
||||
Here is the official kotlin learning - [Kotlin-Learning](https://kotlinlang.org/docs/reference/)
|
||||
|
||||
###### Develop Android & iOS Apps Using Flutter
|
||||
|
||||
[Official Docs](https://flutter.io)
|
||||
|
@ -127,7 +127,7 @@ The Current column shows us the version that is installed locally. The Latest co
|
||||
|
||||
## Managing Dependencies with package.json
|
||||
|
||||
If not using a specific flag and installing a module like `npm install express` will install the module in `node_modules` folder locally but the `package.json` that keep records of every dependency we are using in a project will not be updated with our addition. Thus, the package will be development specific, will not be installed in runtimme environment. Make sure, you always use a proper flag and keep `package.json` file updated.
|
||||
If not using a specific flag and installing a module like `npm install express` will install the module in `node_modules` folder locally but the `package.json` that keep records of every dependency we are using in a project will not be updated with our addition. Thus, the package will be development specific, will not be installed in runtime environment. Make sure, you always use a proper flag and keep `package.json` file updated.
|
||||
|
||||
When you install packages locally, you need a package.json file. To generate one you can do that by using `npm init` command. It will prompt up with some questions that by pressing enter you can keep the default values.
|
||||
|
||||
@ -336,10 +336,10 @@ After every install, upgrade or removal, yarn updates a yarn.lock file which kee
|
||||
|
||||
A first release of a npm package is always 1.0.0
|
||||
|
||||
Bug fixes, or minor changes increment the third digit, hense 1.0.0 would become 1.0.1
|
||||
Bug fixes, or minor changes increment the third digit, hence 1.0.0 would become 1.0.1
|
||||
|
||||
New features that dont break previous versions of a package increment the second digit, hense 1.0.0 would become 1.1.0
|
||||
|
||||
All changes that break the previous releases of a package increment the first digit, hense 1.0.0 would become 2.0.0
|
||||
|
||||
It is important to remember this when updateing packages to keep your project stable!
|
||||
It is important to remember this when updating packages to keep your project stable!
|
||||
|
Reference in New Issue
Block a user