Order of require statements in application.js

Open
#198 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
bootstrap, javascript, jquery, rails
Domain
build-system, frontend

Research direction

Start with the application.js require statements described in the issue and reproduce the Rails 5.2 browser error. Compare the documented order with bootstrap, jquery3, and popper in that file; done means the ordering no longer causes the hasAttribute error and the affected asset setup is verified.

Written by the indexing model from the issue text.

Description

In rails 5.2,

Following document order of require statements causing the

Uncaught TypeError: Cannot read property 'hasAttribute' of null
in browser console

Updating the order to

//= require bootstrap
//= require jquery3
//= require popper

fixed the bug

Dominant language
SCSS
Stars
2k
Forks
437
Avg merge
1h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from twbs/bootstrap-rubygem

All issues in twbs/bootstrap-rubygem

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.