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.

Sign up for GitHub

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

Added note on finding areas that need webpack migration #35241

Merged
merged 2 commits into from
Oct 22, 2024
Merged

Added note on finding areas that need webpack migration #35241

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c569292
Added note on finding areas that need webpack migration
orangejenny Oct 21, 2024
54ec50e
Update docs/js-guide/requirejs-to-webpack.rst
orangejenny Oct 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/js-guide/requirejs-to-webpack.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,15 @@ for a more detailed explanation.
If new ``exports-loader`` statements are added, it is recommended to test the changes on staging to ensure
the functionality is maintained between production and staging.

Step 0: Decide What to Migrate
------------------------------

How do you know what areas have and have not been migrated? Because all pages that bundle javascript use a template
tag to specify the entry point, this template tag is an easy way to tell if a page uses Webpack or RequireJS.

If looking for areas that **need** to be migrated, grepping for ``requirejs_main`` will identify all unmigrated
pages.


Step 1: Update the Template Tag and Add Global ``commcarehq`` Dependency
------------------------------------------------------------------------
Expand Down
Loading