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

Further front-end build cleanup #56

Closed
5 of 6 tasks
thibaudcolas opened this issue Mar 18, 2021 · 11 comments
Closed
5 of 6 tasks

Further front-end build cleanup #56

thibaudcolas opened this issue Mar 18, 2021 · 11 comments

Comments

@thibaudcolas
Copy link
Member

thibaudcolas commented Mar 18, 2021

Follow-up from #43

@Stormheg Stormheg self-assigned this Mar 18, 2021
@tbrlpld
Copy link
Collaborator

tbrlpld commented Mar 22, 2021

Popper is used by bootstrap for certain elements. Not sure we are using any of them.

@lb-
Copy link
Member

lb- commented Mar 30, 2022

Should also try to adopt our shared linting packages if not already in use.

@PaarthAgarwal
Copy link
Member

Which ones should be present in devDependencies?

@lb-
Copy link
Member

lb- commented May 10, 2022

Anything that is client facing should be in dependencies. Anything that relates to the building of the project (Webpack) or working with code that gets transformed before the final build (babel, sass) should be Dev.

But check each one gets used also.

"@fortawesome/fontawesome-free": "^5.13.0", non-dev
"autocompleter": "^6.0.3", non-dev (I think)
"babel-loader": "^8.2.2", DEV
"bootstrap": "^4.4.1", non-dev
"copy-webpack-plugin": "^8.0.0", DEV
"css-loader": "^5.1.2", DEV
"file-loader": "^6.2.0", DEV
"jquery": "^3.5.1", non-dev
"mini-css-extract-plugin": "^1.3.9", DEV
"popper.js": "^1.16.1", non-dev (or not needed)
"sass": "^1.32.8", DEV
"sass-loader": "^11.0.1", DEV
"stylelint": "^13.3.3", DEV
"underscore": "^1.10.2", non-dev
"webpack": "^5.24.4", DEV
"webpack-cli": "^4.5.0" DEV

@lb-
Copy link
Member

lb- commented May 10, 2022

We should also update the package JSON version to match the release version (need to ensure the release instructions includ that).

And add to the list for this issue (or a seperate one) - basic JS unit tests.

@PaarthAgarwal
Copy link
Member

We should also update the package JSON version to match the release version (need to ensure the release instructions includ that).

Currently it says "version": "1.0.0". Should it be updated to 2 .0.0 or 3.0.0?

@PaarthAgarwal
Copy link
Member

Anything that is client facing should be in dependencies. Anything that relates to the building of the project (Webpack) or working with code that gets transformed before the final build (babel, sass) should be Dev.

But check each one gets used also.

"@fortawesome/fontawesome-free": "^5.13.0", non-dev "autocompleter": "^6.0.3", non-dev (I think) "babel-loader": "^8.2.2", DEV "bootstrap": "^4.4.1", non-dev "copy-webpack-plugin": "^8.0.0", DEV "css-loader": "^5.1.2", DEV "file-loader": "^6.2.0", DEV "jquery": "^3.5.1", non-dev "mini-css-extract-plugin": "^1.3.9", DEV "popper.js": "^1.16.1", non-dev (or not needed) "sass": "^1.32.8", DEV "sass-loader": "^11.0.1", DEV "stylelint": "^13.3.3", DEV "underscore": "^1.10.2", non-dev "webpack": "^5.24.4", DEV "webpack-cli": "^4.5.0" DEV

I think we should keep popper.js. Maybe we are not using it right now but it is possible that one day we'll use something from bootstrap that requires popper. We can remove underscore though as Thibaud suggested.

@lb-
Copy link
Member

lb- commented May 11, 2022

I would opt for removing popper personally, we can always add it if we need it.

@lb-
Copy link
Member

lb- commented May 11, 2022

Actually - ignore that package version thing, that is probably just unhelpful and creates confusion.

@PaarthAgarwal
Copy link
Member

I would opt for removing popper personally, we can always add it if we need it.

Sure

@lb-
Copy link
Member

lb- commented May 12, 2022

Last three items have been split to their own issues.

Rest has been done, thanks everyone!

@lb- lb- closed this as completed May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants