Skip to content

Commit

Permalink
Issue #49: Potential fix for yarn build:deploy not exiting:
Browse files Browse the repository at this point in the history
This adds an intentionally invalid SCSS to test:

- Upgrading drupal/omnipedia_site_theme (7.x-dev bd7603e => 7.x-dev 30aaaea)
  • Loading branch information
Ambient-Impact committed Apr 25, 2024
1 parent d3f7a70 commit 904bf24
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 4 deletions.
6 changes: 6 additions & 0 deletions .do/build/yarn.sh
Original file line number Diff line number Diff line change
Expand Up @@ -16,4 +16,10 @@
# Tells App Platform to install jq for us.
yarn add $(jq --raw-output '.composerDependencies | to_entries[] | [.key, .value] | [join("@")] | join(" ")' package.json)

# For whatever reason, running this package.json script doesn't correctly fail
# the whole process if the script fails. This is probably related to using
# cross-env. Note that we have to return the return value to correctly stop
# execution of the parent script on build failure, via the subsequent command.
yarn build:deploy

return "$?"
8 changes: 4 additions & 4 deletions composer.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit 904bf24

Please sign in to comment.