Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
doi-landing-page
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ICAT
  • doi-landing-page
  • Issues
  • #87

Closed
Open
Opened Nov 20, 2020 by Maxime Chaillet@mchaille
  • Report abuse
  • New issue
Report abuse New issue

Do we need bower + npm ?

This project uses bower + npm package managers.

The dependencies added by bower are:

"jquery": "^3.2.1",
    "dustjs-linkedin": "^2.7.5",
    "bootstrap": "^4.0.0",
    "dustjs-helpers": "^1.7.3",
    "lodash": "^4.17.5",
    "moment": "momentjs#^2.21.0"

They could be managed by npm instead, and then we could drop bower. On top of that, bower's maintainers recommend to drop it and use another one instead (yarn)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: icat/doi-landing-page#87