Issues with Lab 6.2 (Is ^2.0.0 really the same as 2.0.0)

Background info not required for my question further down
Unfortunately, the previous discussion was closed: https://forum.linuxfoundation.org/discussion/856809/issues-with-lab-6-2
However, I am still having an issue with this, in a way which hasn't yet been raised. I'm sure I'm missing some understanding here, but I need to know how the packaging system properly works.
To be clear, I understand that part of the previous discussion was regarding an update to the testing code. I have no issue with that. I also understand how and why the fastify dependency within package.json needs to be defined as "fastify": "^2.0.0"
.
My question
What I don't understand is how "fastify": "^2.0.0"
will actually ever install a version "greater than or equal to 2.0.0, while accepting all future MINOR and PATCH versions".
- It begins by installing exactly 2.0.0.
- After running
npm i
it doesn't progress beyond version 2.0.0. - After deleting the node_modules directory and
npm i
it reinstalls version 2.0.0. - After deleting the package-lock.json and
npm i
it reinstalls version 2.0.0.
I trust you understand my confusion here. What is the point in defining a version above 2.0.0, if all it will ever install is version 2.0.0? What is the point in the caret (^)?
In fact, only after deleting the node_modules directory AND the package-lock.json, will it finally install a version greater than 2.0.0, when I npm i
. Is this the intention - do we have to delete things to make the system work?
Or am I misunderstanding how the system works?
Thank you,
Malc
Comments
-
Hey Malc
Yeah it's the package-lock.json. By default the npm client adds that when you first install then locks in the dependencies. Personally I have this turned off, as you say it defeats the point of semver.
The point of lock file is to set a point in time where you lock deps for deployment purposes. Even if you take patch and minor updates you still have to trust that everyone is abiding by the bug fix/backwards compat api updates and not breaking things. Package-lock is useful for those situations where you have a large application and you want to now manually control when deps are updated. Using it from the start of a project, or for small modules, makes no sense to me personally. Imo the package-lock file should not be on by default, but that is something to take up with npm.
You can turn off package-lock with
npm config set package-lock false
And then when you actually want a package lock, you can do npm install --package-lock
1 -
Many thanks for explaining that, David.
It all makes perfect sense; equally, your thought, that package-lock should really be off by default.
I entirely agree with you and am going to follow your logic, turning it off until required.
Thank you!
Malc
0 -
np malc!
0
Categories
- 8.8K All Categories
- 12 LFX Mentorship
- 65 LFX Mentorship: Linux Kernel
- 356 Linux Foundation Boot Camps
- 226 Cloud Engineer Boot Camp
- 69 Advanced Cloud Engineer Boot Camp
- 23 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 724 Training Courses
- 14 LFC110 Class Forum
- 16 LFD102 Class Forum
- 96 LFD103 Class Forum
- 2 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 14 LFD254 Class Forum
- 420 LFD259 Class Forum
- 78 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 15 LFS200 Class Forum
- 683 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 23 LFS241 Class Forum
- 26 LFS242 Class Forum
- 18 LFS243 Class Forum
- 4 LFS244 Class Forum
- 7 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 103 LFS253 Class Forum
- 753 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 48 LFS260 Class Forum
- 74 LFS261 Class Forum
- 6 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 8 LFS268 Class Forum
- 4 LFS269 Class Forum
- 173 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 184 LFW211 Class Forum
- 99 LFW212 Class Forum
- 875 Hardware
- 204 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 716 Linux Distributions
- 78 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 125 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 344 Ubuntu
- 445 Linux System Administration
- 33 Cloud Computing
- 63 Command Line/Scripting
- Github systems admin projects
- 88 Linux Security
- 73 Network Management
- 105 System Management
- 45 Web Management
- 50 Mobile Computing
- 18 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 499 Off Topic
- 119 Introductions
- 193 Small Talk
- 19 Study Material
- 742 Programming and Development
- 237 Kernel Development
- 471 Software Development
- 898 Software
- 244 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 313 Installation
- 19 All In Program
- 19 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)