Timeline for How is a reproducible build guaranteed with version ranges in NPM?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2020 at 22:53 | history | edited | curiousdannii | CC BY-SA 4.0 |
typo
|
| Aug 18, 2020 at 15:53 | vote | accept | Finlay Weber | ||
| Aug 13, 2020 at 15:40 | comment | added | Jörg W Mittag | Only if you explicitly tell it to re-resolve the dependencies. But then, you explicitly asked for it. Note that if your build process is changing files inside of the repository, you have much bigger problems than worrying about version ranges. | |
| Aug 13, 2020 at 15:37 | comment | added | Finlay Weber | But the processes of building on the build server cant lead to downloading a newer version of a dependency, which sure will also update the lockfile, hence such a build is no longer identical to the build at the point where the developer checked in the code. Right? or am I looking at this the wrong way? | |
| Aug 13, 2020 at 15:13 | history | answered | curiousdannii | CC BY-SA 4.0 |