Why not put "node": ">=6" ?
Scrum
All 11 comments
I had to downgrade some packages fix the versions for:
"postcss-preset-env": "6.6.0","stylelint": "11.0.0","autoprefixer": "9.5.1",
Scrum
on 23 Jun 2020
Because Node.js never was a LTS version and do not receive security updates.
Why you locked on this version?
ai
on 23 Jun 2020
The reason of changing engines is that some Node.js versions contained the bug
ai
on 23 Jun 2020
Because Node.js never was a LTS version and do not receive security updates.
Why you locked on this version?
At the moment, we are stuck on this version and for migration to the nodes above we will need a lot of resources.
Yes, we will migrate, but we needed to know that this would happen in order to prepare for this in advance. Now we鈥檒l be great forced to throw all resources to correct this situation
it is also worth understanding that in large companies the most difficult is the migration of all those who indirectly do manual assembly, yes we still collect bundles by hand, I think like most large companies with big legacy
Scrum
on 23 Jun 2020
Why did you stuck on non-LTS version?
ai
on 23 Jun 2020
Why did you stuck on non-LTS version?
I think there were two circumstances:
- Spontaneous implementation of new tools
- The period of floating developers
- The lack of a leader at that time
Scrum
on 23 Jun 2020
I think that such an update should have carried a major version
Just recently, I had the same carelessness of updating for posthtml
Scrum
on 23 Jun 2020
Good point about breaking changes 8d6c6cc
But you should spend this time on updates Nodejs 11 to 12. Fixing Autoprefixer is like fixing the symptoms instead of the source of the problem. The problem is sticking on the non-LTS version.
ai
on 23 Jun 2020
Released in 9.8.3
ai
on 23 Jun 2020
But you should spend this time on updates Nodejs 11 to 12. Fixing Autoprefixer is like fixing the symptoms instead of the source of the problem. The problem is sticking on the non-LTS version.
Of course, we are moving towards this, but in this case it was spontaneous for us and we did not take the very right measures, unfortunately at the moment they are necessary and we must now review the entire large project and slow down the overall processes which will not have a very positive effect on the product
Scrum
on 23 Jun 2020
Released in 9.8.3
Thank you for understanding 馃殌
Scrum
on 23 Jun 2020
Related issues
plesiecki
路
4Comments
flying-sheep
路
4Comments
yuheiy
路
5Comments
umakantp
路
5Comments
leoj3n
路
7Comments
Most helpful comment
Released in 9.8.3