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
- All Categories
- 112 LFX Mentorship
- 112 LFX Mentorship: Linux Kernel
- 604 Linux Foundation IT Professional Programs
- 315 Cloud Engineer IT Professional Program
- 139 Advanced Cloud Engineer IT Professional Program
- 52 DevOps Engineer IT Professional Program
- 67 Cloud Native Developer IT Professional Program
- 3 Express Training Courses
- 3 Express Courses - Discussion Forum
- 5.3K Training Courses
- 17 LFC110 Class Forum - Discontinued
- 8 LFC131 Class Forum
- 30 LFD102 Class Forum
- 178 LFD103 Class Forum
- LFD110 Class Forum
- 24 LFD121 Class Forum
- LFD133 Class Forum
- 2 LFD137 Class Forum
- 62 LFD201 Class Forum
- 2 LFD210 Class Forum
- 1 LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 127 LFD232 Class Forum - Discontinued
- LFD233 Class Forum
- LFD237 Class Forum
- 22 LFD254 Class Forum
- 643 LFD259 Class Forum
- 107 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 4 LFD273 Class Forum
- 1 LFS101 Class Forum
- LFS112 Class Forum
- LFS116 Class Forum
- LFS118 Class Forum
- LFS144 Class Forum
- 2 LFS145 Class Forum
- LFS151 Class Forum
- LFS157 Class Forum
- LFS158 Class Forum
- LFS162 Class Forum
- LFS167 Class Forum
- 28 LFS200 Class Forum
- 735 LFS201 Class Forum - Discontinued
- 1 LFS201-JP クラス フォーラム
- 13 LFS203 Class Forum
- 98 LFS207 Class Forum
- 299 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 36 LFS243 Class Forum
- 12 LFS244 Class Forum
- LFS245 Class Forum
- 41 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 141 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 2 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 109 LFS260 Class Forum
- 144 LFS261 Class Forum
- 39 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 20 LFS267 Class Forum
- 18 LFS268 Class Forum
- 26 LFS269 Class Forum
- 198 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 254 LFW211 Class Forum
- 173 LFW212 Class Forum
- 9 SKF100 Class Forum
- SKF200 Class Forum
- 781 Hardware
- 198 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 174 Networking
- 87 Printers & Scanners
- 83 Storage
- 742 Linux Distributions
- 80 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 23 openSUSE
- 143 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 347 Ubuntu
- 450 Linux System Administration
- 31 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 101 System Management
- 46 Web Management
- 51 Mobile Computing
- 18 Android
- 23 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 355 Off Topic
- 109 Introductions
- 167 Small Talk
- 18 Study Material
- 504 Programming and Development
- 283 Kernel Development
- 203 Software Development
- 844 Software
- 210 Applications
- 180 Command Line
- 3 Compiling/Installing
- 107 Games
- 308 Installation
- 51 All In Program
- 51 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)