-
Notifications
You must be signed in to change notification settings - Fork 30
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
Support custom builder in cordova-serve #108
Comments
I think I have related issue. Just added support for custom webpack configuration using that article https://www.techiediaries.com/ionic-angular-typeorm-custom-webpack-configuration/ and have it working for |
Hi there! Is this still an issue?With the latest updates to the new builder API, this should be supported as the browserBuild is an option that can be passed
|
@mhartington working now! Good job 👍👍👍 |
@mhartington, I don't fully understand your comment. When you say |
Sorry,
These could be any task in your angular.json. For example, the default
Which in turn resolves to the default If you wanted to customize this, you could do the following.
|
please add support custom-webpack |
I am facing the same issue. My webpack configuration from build task is ignored by ionic-cordova-serve task. |
Same issue, is there a solution? |
Going to close this. As I mentioned here #230 (comment) We need to be explicit about what kind of builder we trigger. |
HI! Any updates on this? I'm really struggling on this 😞 |
In the resolution of issue #32 the capability was added to use browserTarget to specify an arbitrary builder that the
cordova-build
builder wraps. It would be very helpful to have the analogous capability forcordova-serve
: rather than hardcodingDevServerBuilder
and extending it, usegetBuilder
to pick up a specified builder.It looks, however, like this might not be possible with Angular Architect as it stands now: their
DevServerBuilder
seems to be grabbing the browser build options out of the specifiedbrowserTarget
, and doing so internally withinrun()
. That would make an override ofbuildWebpackConfig()
the only place where the browser build options are accessible to modify...and this is not part of theBuilder<>
interface, only ofDevServerBuilder
, so this strategy doesn't work for an arbitrary Builder loaded by Architect.Does this seem right - and if so, is there any resolution coming with the new Angular build API? I haven't been able to find any documentation on the new API, so hard to tell what might be changing with it. This problem throws a bit of a wrench into my development, because my project (which builds for both Cordova and Electron with a single codebase) relies on a custom webpack config to ignore imports of node-provided modules like
fs
when building for Angular.The text was updated successfully, but these errors were encountered: