Closed (fixed)
Project:
Drupal core
Version:
8.6.x-dev
Component:
javascript
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Sep 2017 at 01:15 UTC
Updated:
12 Feb 2018 at 06:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
GrandmaGlassesRopeMan@droplet I had created #2895713: Update Babel and babel-preset-env to their latest versions which should probably just be updated with this information.
Comment #3
droplet commentedComment #4
droplet commentedThe build script has a compatible error with node 8.8.0+
Comment #5
GrandmaGlassesRopeManOk. This looks good. I tested this locally and didn't see any build-time changes. 👍
Comment #6
xjmUpdating issue credit.
Comment #7
xjmThanks for the patch! I think this should probably go into 8.5.x only.
This one looks like a major update; can we check and confirm what BC breaks if any this package might have?
It's probably okay but we should ask the question each time.
Comment #8
GrandmaGlassesRopeManThere's just,
Scripts using quotes or escape sequences will see a difference in behavior., which was noted in the5.0.0release notes. We aren't doing that so it should not be an issue.Comment #9
droplet commentedTechnically, there are no BC breaks in NodeJS packages we have to check.
For non-CORE scripts, they should always specify the version in their own package.json rather than include the ref packages from another package. And you need to call the script command in the CORE package rather than modify it directly. It's independent.
It reminds me to check the scripts in "core\scripts\js", I, myself do not expect anyone to include these files into their own scripts.
Comment #10
xjmThanks @drpal and @droplet.
Let's at least add a CR about this issue that covers #8 and maybe also reminds site owners to check this and maybe includes some reminder about #9. Once we have that, I think this is okay for a minor release.
Probably we should also mention it 8.5.x release notes (with a link to the CR) in case someone is doing something strange.
Comment #11
GrandmaGlassesRopeMan- cr => https://www.drupal.org/node/2925008
Comment #13
xjmWhoops, looks like this missed getting its needed review. I made some small edits to the CR; looks good.
Comment #14
GrandmaGlassesRopeMan@xjm Since this sat at needs review for so long some of the updates to the dependencies are probably out of date.
Comment #15
xjmah, Can we update it then? I imagine this would be something to get in before beta. What would the consequences be of being on the old packages throughout 8.5?
Comment #16
droplet commentedI think we should add "^" (ref) before all packages
Then to run:
Comment #17
GrandmaGlassesRopeMan- set caret ranges on all packages
- update versions of other things that have changed
Comment #18
justafish👍
Comment #20
GrandmaGlassesRopeManAlright, a few strange things are happening,
- the php yaml parser doesn't like this config file,
- why are we testing yaml files within the
node_modulesdirectory? those are all javascript dependencies?Comment #21
GrandmaGlassesRopeManComment #24
lauriiiTested manually the build tools and checked for any unexpected changes in the compiled JS. Everything looked normal since there was no changes in the compiled JS at all.
The major release that @xjm had already pointed on #7 also caught my eye. I checked the release notes to make sure we are not affected. I came to same conclusion as @drpal did on #8.
Committed to 8.6.x and cherry-picked to 8.5.x. Thanks!