[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title Cliff Meyers commented on JENKINS-40206 Re: Eliminate shrinkwrap pain To add to the prior point, my recollection is that since shrinkwrap holds fully-qualified URL's to each artifact, the registry being used at the time of shrinkwrapping in what npm will use. We had experimented with doing a search/replace for the main registry path in shrinkwrap.json which I believe did work - perhaps Yoann Dubreuil can confirm. However it's not great since a CI build would behave differently from the user's local machine, unless each developer configured their npmrc file to use the same registry. My recollection is that Yarn wouldn't have this problem, as the Lockfiles do not specify URL's and I know it supports registries (see: https://github.com/yarnpkg/yarn/issues/606 ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title Tom FENNELLY commented on JENKINS-40206 Re: Eliminate shrinkwrap pain Has also been pointed out to us (by Yoann Dubreuil ) that we can't use an NPM registry (or there are serious issues using one) because of shrinkwrap. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title Cliff Meyers commented on JENKINS-40206 Re: Eliminate shrinkwrap pain This project might be looking at as well, from the yarn guys: https://lernajs.io/ I haven't dug deep on it yet but it seems related to things we are doing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Cliff Meyers
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc) can take ages i.e. can take up to an hour (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).## I (CM) believe I'd had that working fine provided I set a new/beta version in the module I'm installing, install it, then slink it. (see comment below) # Works with maven build - we will need some changes here I think ... not sure if frontend will work for anything other than npm when it comes to installing packages.h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.## Yarn uses a lockfile by default, and has explicit commands that differentiate between adding a dependency (add) and installing a project's dependencies (install).## Yarn supports link/unlink, so it may eliminate the need for slink## Link to commit/branch in the JDL where I experimented using yarn: https://github.com/jenkinsci/jenkins-design-language/commit/2538a4f08be8ec5adc99d41b09c975ba49dbbc94# Write some node.js scripts that help streamline npm/shrink operations, and perform additional validation (some of validation already exists and is called from the Jenkinsfile)## I (CM) find the trickiest scenario to manage is when there is a conflict during merge. I usually follow this process:### Accept "theirs" for package.json and npm-shrinkwrap.json### Run "npm install" so that package.json, npm-shrinkwrap.json and node_modules are in sync### Individually install the correct version of each package that I have changed: "npm install cliff-code@1.5.2 -S -E"### We could write a script that does this? Perhaps one that does it across multiple/all modules at once? For example, we could use "./setlib.js blueocean-core-js@1.5.2" which would step into all projects, find those which depend on "blueocean-core-js" and run the correct install command in each# Give up on JS package management entirely and just
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title Cliff Meyers edited a comment on JENKINS-40206 Re: Eliminate shrinkwrap pain [~tfennelly] you're right, slinking is messier than I'd hoped. You have to do the following:# # Set a new version in the package.json of the module you're working on# # Hand-edit the package.json and npm-shrinkwrap.json of the module(s) that depend on it# # Run slink from those modules Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title Cliff Meyers commented on JENKINS-40206 Re: Eliminate shrinkwrap pain Tom FENNELLY you're right, slinking is messier than I'd hoped. You have to do the following: Set a new version in the package.json of the module you're working on Hand-edit the package.json and npm-shrinkwrap.json of the module(s) that depend on it Run slink from those modules Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc) can take ages i.e. can take up to an hour (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).## I (CM) believe I'd had that working fine provided I set a new/beta version in the module I'm installing, install it, then slink it.# Works with maven build - we will need some changes here I think ... not sure if frontend will work for anything other than npm when it comes to installing packages .h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.## Yarn uses a lockfile by default, and has explicit commands that differentiate between adding a dependency (add) and installing a project's dependencies (install).## Yarn supports link/unlink, so it may eliminate the need for slink## Link to commit/branch in the JDL where I experimented using yarn: https://github.com/jenkinsci/jenkins-design-language/commit/2538a4f08be8ec5adc99d41b09c975ba49dbbc94# Write some node.js scripts that help streamline npm/shrink operations, and perform additional validation (some of validation already exists and is called from the Jenkinsfile)## I (CM) find the trickiest scenario to manage is when there is a conflict during merge. I usually follow this process:### Accept "theirs" for package.json and npm-shrinkwrap.json### Run "npm install" so that package.json, npm-shrinkwrap.json and node_modules are in sync### Individually install the correct version of each package that I have changed: "npm install cliff-code@1.5.2 -S -E"### We could write a script that does this? Perhaps one that does it across multiple/all modules at once? For example, we could use "./setlib.js blueocean-core-js@1.5.2" which would step into all projects, find those which depend on "blueocean-core-js" and run the correct install command in each# Give up on JS package management entirely and just check things into
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc) can take ages i.e. can take up to an hour (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).## I (CM) believe I'd had that working fine provided I set a new/beta version in the module I'm installing, install it, then slink it. # Works with maven build - we will need some changes here I think ... not sure if frontend will work for anything other than npm. h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.## Yarn uses a lockfile by default, and has explicit commands that differentiate between adding a dependency (add) and installing a project's dependencies (install).## Yarn supports link/unlink, so it may eliminate the need for slink## Link to commit/branch in the JDL where I experimented using yarn: https://github.com/jenkinsci/jenkins-design-language/commit/2538a4f08be8ec5adc99d41b09c975ba49dbbc94# Write some node.js scripts that help streamline npm/shrink operations, and perform additional validation (some of validation already exists and is called from the Jenkinsfile)## I (CM) find the trickiest scenario to manage is when there is a conflict during merge. I usually follow this process:### Accept "theirs" for package.json and npm-shrinkwrap.json### Run "npm install" so that package.json, npm-shrinkwrap.json and node_modules are in sync### Individually install the correct version of each package that I have changed: "npm install cliff-code@1.5.2 -S -E"### We could write a script that does this? Perhaps one that does it across multiple/all modules at once? For example, we could use "./setlib.js blueocean-core-js@1.5.2" which would step into all projects, find those which depend on "blueocean-core-js" and run the correct install command in each# Give up on JS package management entirely and just check things into node_modules.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Cliff Meyers
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc) can take ages i.e. can take up to an hour (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).## I (CM) believe I'd had that working fine provided I set a new/beta version in the module I'm installing, install it, then slink it.h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.## Yarn uses a lockfile by default, and has explicit commands that differentiate between adding a dependency (add) and installing a project's dependencies (install).## Yarn supports link/unlink, so it may eliminate the need for slink# # Link to commit/branch in the JDL where I experimented using yarn: https://github.com/jenkinsci/jenkins-design-language/commit/2538a4f08be8ec5adc99d41b09c975ba49dbbc94# Write some node.js scripts that help streamline npm/shrink operations, and perform additional validation (some of validation already exists and is called from the Jenkinsfile)## I (CM) find the trickiest scenario to manage is when there is a conflict during merge. I usually follow this process:### Accept "theirs" for package.json and npm-shrinkwrap.json### Run "npm install" so that package.json, npm-shrinkwrap.json and node_modules are in sync### Individually install the correct version of each package that I have changed: "npm install cliff-code@1.5.2 -S -E"### We could write a script that does this? Perhaps one that does it across multiple/all modules at once? For example, we could use "./setlib.js blueocean-core-js@1.5.2" which would step into all projects, find those which depend on "blueocean-core-js" and run the correct install command in each# Give up on JS package management entirely and just check things into node_modules.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Cliff Meyers
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc) can take ages i.e. can take up to an hour (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s). ## I (CM) believe I'd had that working fine provided I set a new/beta version in the module I'm installing, install it, then slink it. h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}. # Works with maven build - we will need some changes here I think ... not sure if frontend will work for anything other than npm. h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this. Will def require frontend change ## Yarn uses a lockfile by default, and has explicit commands that differentiate between adding a dependency (add) and installing a project's dependencies (install).## Yarn supports link / replacement unlink, so it may eliminate the need for slink# Write some node . js scripts that help streamline npm/shrink operations, and perform additional validation (some of validation already exists and is called from the Jenkinsfile) # # I (CM) find the trickiest scenario to manage is when there is a conflict during merge. I usually follow this process:### Accept "theirs" for package.json and npm-shrinkwrap.json### Run "npm install" so that package.json, npm-shrinkwrap.json and node_modules are in sync### Individually install the correct version of each package that I have changed: "npm install cliff-code@1.5.2 -S -E"### We could write a script that does this ? Perhaps one that does it across multiple/all modules at once ? For example, we could use "./setlib.js blueocean-core-js@1.5.2" which would step into all projects, find those which depend on "blueocean-core-js" and run the correct install command in each# Give up on JS package management entirely and just check things into node_modules.
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc) can take ages i.e. can take up to an hour (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.# Works with maven build - we will need some changes here I think ... not sure if frontend will work for anything other than npm.h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this. Will def require frontend change/replacement. # ??
Add Comment
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc) can take ages i.e. can take up to an hour (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}. # Works with maven build - we will need some changes here I think ... not sure if frontend will work for anything other than npm. h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.# ??
Add Comment
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc) can take ages i.e. can take up to an hour or more (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.# ??
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap"):# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}} etc ) can take ages i.e. an hour or more (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.# ??
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
Shrinkwrap is an unbearable pain in the ass (locally known as "shrinkcrap") :# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}}) can take ages i.e. an hour or more (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.# ??
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
Shrinkwrap is an unbearable pain in the ass:# It just stops working (without error on install etc) if the version numbers of packages do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm-shrinkwrap.json}}) can take ages i.e. an hour or more (some people have said it takes them multiple hours).# Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I (TF) can remember, it's not possible to use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue(s).h2. Scope# Decent errors when package installs do not do as expected i.e. update relevant build files.# Easy and fast process for getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the roll of {{npm-shrinkwrap.json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}. h2. Possibilities# Switch to using Yarn. [~cliffmeyers] has already done some experimenting with this.# ??
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-40206
Eliminate shrinkwrap pain
Change By:
Tom FENNELLY
The dev process around Blue Ocean and Shrinkwrap is an unbearable pain in the hoops we have to jump through wrt NPM ass:# It just stops working (without error on install etc) if the version numbers of packages is both painful do not line up perfectly in {{package.json}}, {{npm-shrinkwrap.json}} and confusing {{node_modules}}.# Getting it back into a working state (where an {{npm install}} updates {{npm - too easy to screw things up shrinkwrap.json}}) can take ages i.e. an hour or forget to do something more ( publish a package etc some people have said it takes them multiple hours ). Shrinkwrap # Regenration of the {{npm-shrinkwrap.json}} from scratch is a horrible option too because that then results in commit diffs with line change counts in the 1,000s.# From what I ( aka "Shrinkcrap" TF ) is wrecking everyone can remember, it 's head.We need not possible to improve the use tools like {{slink}} or {{linklocal}} when using shrinkwrap. Can't remember the issue ( and maybe create new tools s ) to help smooth and speed the process here . Maybe we should create an Epic for this and break out multiple JIRAs. Anyway h2 . Scope# Decent errors when package installs do not do as expected i . e . this might be my scunkworks project update relevant build files.# Easy and fast process for when I'm bored during my vacation time over getting things back into a working order if things are inconsistent e.g. regeneration of whatever fills the next few weeks roll of {{npm-shrinkwrap . json}} is simple and does not result in line change counts in the 1,000s.# Possible to work in dev mode and use tools like {{slink}} or {{linklocal}}.
Add Comment
[JIRA] (JENKINS-40206) Eliminate shrinkwrap pain
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-40206 Eliminate shrinkwrap pain Change By: Tom FENNELLY Summary: Make the Blue Ocean dev process not suck so much Eliminate shrinkwrap pain Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
