Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #14130 Make possible to build Tuleap on Node.js 12.x
    Actions
    Infos
    #14130
    Thomas Gerbet (tgerbet)
    2019-12-12 17:53
    2019-11-12 09:01
    15323
    Details
    Make possible to build Tuleap on Node.js 12.x
    It is currently not possible to build Tuleap with Node.js 12.x due to multiple issues. I spotted those a while ago but it is going to become more and more annoying because Node.js 12.x is becoming the default for mainstream distributions (such as Fedora 31).

    Two issues spotted for now:
    * our version of node-sass is broken on Node.js 12.x (easily fix, see gerrit #16700)
    * Gulp 3 is deprecated is broken and does not work on Node.js 12.x [0]



    [0] https://github.com/gulpjs/gulp/issues/2324
    Dev tools
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2019-12-12
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #14137 Tuleap Releases 11.10 Delivered 2020-02-07 14:53 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #14130

    Artifact Tracker v5

    request #14472 Update gulp in trackers to v4.x

    Git commit

    tuleap/tuleap/stable

    Update node-sass so it can work on Node.js 12.x b313f5a34a
    User avatar Thomas Gerbet (tgerbet) , 2019-11-12 09:00
    Upgrade to gulp v4 a82914128f
    User avatar Joris MASSON (jmasson) , 2019-12-12 17:11
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2019-12-12 17:53
    gerrit #11544 (Gulp v4) integrated into Tuleap 11.9.99.7.

    Thanks for dealing with the upgrade @jmasson.


    Sources can now be built with node 12.
    • Status changed from Under implementation to Closed
    • Connected artifacts
    • Close date set to 2019-12-12
    User avatar
    Thomas Gerbet (tgerbet)2019-11-12 10:10
    There is still a not negligible amount of work that needs to be done for Webpack so yes migrating to Gulp 4 is probably our only viable solution for now :/ .
    User avatar
    Joris MASSON (jmasson)2019-11-12 09:38
    I have a half-done patch sitting around in gerrit to migrate to Gulp 4, I could share it or start working again on it.
    I'm not up-to-date on our progress for webpack but it feels like there are still a lot of configurations to be written. I'm ok with migrating to Gulp v4 to unblock people faster.
    User avatar
    Thomas Gerbet (tgerbet)2019-11-12 09:06
    For the issue regarding Gulp 3, I was hopping we would have moved to Webpack to build our things and to something like Lerna to act as the glue but request #13299 is not yet closed so it's unlikely to happen on short term. It looks like we need to migrate to Gulp 4.

    @jmasson an opinion on this one?