@mcjaeger @sjha2048 Here is the outline of the work that I am planning to do for the PR targeting this issue.

Refactoring outline

src/components/
- BrowseUploadsHeader:
  - The <Link></Link> componenent can be taken out as a separate component.
- Header:
  - The <Nav.Link></Nav.Link> componenent can be taken out as a separate component -> (not much impact on the file size)
  - The <NavDropdown></NavDropdown> componenents can be taken out as a separate component -> (Major impact on file size).
    Routes and Names for <NavDropdown.Item></NavDropdown.Item> can be loaded from a map present in an external .js file thereby further reducing the file size.
  - The nested <DropdownButton></DropdownButton> in some NavDropdown.Item can also be extracted as a separate component.
- Table:
  - The <div className="paginationTable"> can be extracted out as a separate component.
- Upload\CommonFields:
  - The UploadReuse component contains two different groups of <InputContainer> namely select type and Checkbox type which can be efficiently refactored into two separate components.
src/pages/

This folder also contains many components that can be refactored like Admin/Users/Delete, Browse, Jobs/ScheduleAgents but instead of creating a bulk PR, I'll be just focusing on refactoring the files present in the src/components folder.

Please let me know your views on this.

Refactor large components #108