Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements to Webpack Config #50

Closed
10 tasks done
Tracked by #25 ...
Aveline-art opened this issue Dec 2, 2021 · 5 comments · Fixed by #323
Closed
10 tasks done
Tracked by #25 ...

Improvements to Webpack Config #50

Aveline-art opened this issue Dec 2, 2021 · 5 comments · Fixed by #323
Assignees
Labels
feature: Architecture Pertains to project architecture and settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: frontend Pertains to frontend tasks size: 3pt Can be done in 31-48 hours

Comments

@Aveline-art
Copy link
Member

Aveline-art commented Dec 2, 2021

Dependency

Overview

As a developer, we need to create an environment that will ease development as well as provide users a seamless experience when using our website. For this issue we will configure webpack with several improvements that will improve the overall quality of our project.

Action Items

  • Change webpack config to have the follow improvements. If they already exist, be sure to check them off
    • Production environment
    • Sass loaders
    • Babel loaders
    • HtmlWebpackPlugin
    • Minifying
    • Tree Shaking
    • SVG and other image extensions management
  • Release Add lazy loading capabilities to our codebase #190

Resources/Instructions

Webpack Concepts
Webpack Configuration
Webpack Guides
Webpack Loaders

@Aveline-art Aveline-art added role: backend Pertains to backend tasks size: 3pt Can be done in 31-48 hours labels Dec 2, 2021
@Aveline-art Aveline-art added dependency This item depends on something and removed dependency This item depends on something labels Dec 7, 2021
@Aveline-art Aveline-art added the feature: Architecture Pertains to project architecture and settings label Dec 11, 2021
@Aveline-art Aveline-art self-assigned this Mar 30, 2022
@Aveline-art
Copy link
Member Author

Aveline-art commented Mar 30, 2022

I am taking this issue as part of this must be done concurrently with my work on #78 , since the scope of that issue has expanded

@Aveline-art Aveline-art removed their assignment Mar 31, 2022
@Aveline-art Aveline-art added role: frontend Pertains to frontend tasks and removed role: backend Pertains to backend tasks labels Mar 31, 2022
@gjagnoor gjagnoor self-assigned this Oct 12, 2022
@Aveline-art
Copy link
Member Author

Aveline-art commented Oct 16, 2022

@gjagnoor Is this in progress? Why is it in links/questions/review?

@gjagnoor
Copy link
Member

@Aveline-art Not really, just making final edits you suggested as part of the code review last night. It's there to inform the team that this issue is now under review. Did I misunderstand the purpose of this bin?

@Aveline-art
Copy link
Member Author

@gjagnoor Yes. We don't really use it right now, but historically, it is only used if you need product/stakeholder opinion on your ticket, and only if you could not get that feedback over slack.

@Aveline-art
Copy link
Member Author

Closed because ticket is completed

@ExperimentsInHonesty ExperimentsInHonesty added the PBV: dev all issues for engineering roles (devops, backend, frontend, db) label Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: Architecture Pertains to project architecture and settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: frontend Pertains to frontend tasks size: 3pt Can be done in 31-48 hours
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants