app-webpack error when "quasar build -m bex" after upgrading to @quasar/app-webpack-v3.4.6 #12969
Labels
bug/0-needs-info
Need more info to reproduce
flavour/quasar-cli-webpack
kind/bug 🐞
mode/bex
Qv2 🔝
Quasar v2 issues
What happened?
Yesterday I was upgrading to @quasar/app-webpack-v3.4.6 and quasar-v2.6.2.
Before upgrading I was able to build BEX and the
dist
directory containsPackaged
subdirectory which is containschrome
andfirefox
subdirectories.After upgraded, I saw errors on build outputs below.
And
Packaged
directory did not created by build command.This issue is confirmed because when I tried to create new BEX project with
yarn create quasar
, thenquasar mode add bex
andquasar build -m bex
, I saw the same error.What did you expect to happen?
I expected to be able to publish the browser extension from
Packaged
directory, which is not created by latest version of @quasar/app-webpack-v3.4.6.Reproduction URL
local
How to reproduce?
yarn create quasar
quasar mode add bex
quasar build -m bex
Flavour
Quasar CLI with Webpack (@quasar/cli | @quasar/app-webpack)
Areas
BEX Mode
Platforms/Browsers
No response
Quasar info output
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: