Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Issues
  • #36916
Closed
Open
Issue created Aug 06, 2022 by Administrator@rootContributor

Bootstrap 5.2 - Any JS dependency changes?

Created by: chrisreddington

Discussed in https://github.com/twbs/bootstrap/discussions/36881

Originally posted by chrisreddington August 2, 2022 Hi Folks,

I wondered if anyone had any issues upgrading from Bootstrap 5.2 to 5.2? I'm aware that there were some changes on the sass side (so have imported the new maps partial), but seem to also be having issues with JavaScript.

I can't see anything called out in the Bootstrap 5.2 migration guide around JavaScript. I had a site with JavaScript that was working in 5.1, and now no longer working in 5.2. I am now seeing Uncaught TypeError: Class extends value undefined is not a constructor or null in my console, which hints to me that there's a dependency issue.

The theme itself for my site is hosted in my hugo creator repository, where you'll notice the example/demo site has the exact same issue (which could imply the issue on my end, and how i'm referencing the files - but haven't quite got that stage of identifying the issue yet!)

I'm referencing the individual files from node_modules, via the js/dist folder. The order that I'm referencing is -

"dom/data.js", "dom/event-handler.js", "dom/manipulator.js", "dom/selector-engine.js", "popper.js", "base-component.js", "carousel.js", "collapse.js", "dropdown.js"

Is there anything that I may need to consider going into 5.2 about the ordering of references for the individual components, or any dependency conflicts with other packages that may have been introduced?

Thanks!

Assignee
Assign to
Time tracking