Order of require statements in application.js
Open
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 2k
- Forks
- 437
- Avg merge
- 1h
- Merged PRs (30d)
- 1
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- bootstrap, javascript, jquery, rails
- Domain
- build-system, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100