Releases: Dev-Thought/nx-plugins
Releases · Dev-Thought/nx-plugins
Support custom webpack for angular applications
Feature
- custom webpack support for angular applications are supported now (#65 thx to @kleberksms )
Update ncc owner package
The dependency @zeit/ncc is available under @vercel/ncc now
Fixes for Nx DeployIt
Fix:
- Enable cors "*" per default for Azure Functions
Angular Universal for Google Cloud Platform
Feature
- add Angular Universal support google cloud platform
- add permission rights for google cloud functions invocation. Not necessary to do it manually anymore.
Angular Universal is here
Features
- Support of angular universal for AWS and Azure (GCP will follow).
Bugfixes
- azure express wrong import
- azure remove suffix api from deployment
- azure moved to file sync based and removed own implementation
- webapp add mime package to all
Predictive Setup & Serverless NestJS for AWS
We are happy to announce a new release with great features!
- Support for predictive setup
- NestJS supports deployments on AWS lambda via API Gateway
Predictive Setup
ng-deploy-it autodetects supported applications after ng add and asks you which one you want to set up for deployment. For NX native user the schematic @dev-thought/ng-deploy-it:predictive-setup must be invoked after the package was installed.
Support for nx native cli and ng cli
- refactor: pulumi dep is installed by ng-deploy-it now
- refactor: ng-add is renamed in predictive-setup now
- refactor: predictive-setup has ng-add as an alias (preparing #23 )
New abstraction layer for development
- refactor: init schematic to abstract adapters and remove pulumi interaction and use own
- feat: adjust deploy job with new config
- feat: pulumi config can be found in angular.json now and will be used on deployments and destroys
Now it is much easier to adapt to other application types.
NestJS support for google cloud platform
- feat: add GCP support for nestjs deployment
- feat: update pulumi to the newest version
Deploy NestJS on Azure now!
- add support to deploy NestJS in Azure as azure function
- add support for multiple stacks (stack name contains project name now)