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

build: npm run webpack (WIP) #32721

Closed

Conversation

kdmccormick
Copy link
Member

No description provided.

@kdmccormick kdmccormick changed the title build: npm run webpack build: npm run webpack (WIP) Jul 14, 2023
kdmccormick and others added 5 commits July 18, 2023 12:55
…RE-MERGE)

Re-merge of 4b64d83

The commit after this one contains the fix for the issue that led to the
revert.
Two fixes:

* In the Dockerfile, add copy-node-modules.sh before `npm install`,
  since it is needed by the new postinstall hook.
* In paver/assets.py, run copy-node-modules.sh for backwards com-
  patibility, just for cases where `SKIP_NPM_INSTALL` is enabled
  (which would prevent our new postinstall hook from running
  automatically!). We will deprecate the paver asset commands all at
  once once the new non-paver stuff is 100% working.
TODO: will copy in commit message from PR when squash merging

Part of: openedx#32481
TODO: will copy in commit message from PR when squash-merging

Part of: openedx#32481
TODO: will copy in commit message from PR when squash-merging

Part of: openedx#31604
@kdmccormick kdmccormick force-pushed the kdmccormick/npm-run-webpack branch from 83795ed to 2fb96b2 Compare July 20, 2023 13:49
@kdmccormick
Copy link
Member Author

closed in favor of #32823

@kdmccormick kdmccormick deleted the kdmccormick/npm-run-webpack branch July 24, 2023 17:51
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

Successfully merging this pull request may close these issues.

1 participant