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

Juniper Upgrade - Fix the front end asset build #353

Merged
merged 2 commits into from
May 30, 2021

Conversation

johnbaldwin
Copy link
Contributor

There were a couple of problems

  1. The multi-build.js would not call the second call in `require('./build.js')
  2. Assets were not being created in the path specified by the 'FIGURES_APP_BUILD' directory

This PR fixes those and sets the default build target, npm run build to build both sets of assets for each of the REM_BASE=10 and REM_BASE=16 environments.

There were a couple of problems

1. The multi-build.js would not call the second call in
`require('./build.js')
2. Assets were not being created in the path specified by the
'FIGURES_APP_BUILD' directory

This PR fixes those and sets the default build target, `npm run build`
to build both sets of assets for each of the REM_BASE=10 and REM_BASE=16
environments
@johnbaldwin johnbaldwin merged commit d3f5f4e into master May 30, 2021
@johnbaldwin johnbaldwin deleted the john/fix-fe-asset-build branch May 30, 2021 09:21
@bryanlandia
Copy link
Contributor

Awesome to start work today and see this fixed! Was running into an issue last Thu trying to deploy a temp branch to a Hawthorn server

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.

4 participants