forked from angular-schule/ngx-deploy-starter
-
-
Notifications
You must be signed in to change notification settings - Fork 15
feat!: remove internal build process #527
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d84e6c1
to
02b7ccb
Compare
dianjuar
commented
Aug 29, 2023
bae856b
to
f245f6f
Compare
dianjuar
commented
Sep 1, 2023
af3f150
to
6154513
Compare
Kudos, SonarCloud Quality Gate passed! |
831b78e
to
c217c33
Compare
d035390
to
1259665
Compare
a693fbe
to
8b3ddb3
Compare
dianjuar
commented
Nov 25, 2023
277d9ea
to
608ca5b
Compare
5106182
to
64550f8
Compare
SonarCloud Quality Gate failed.
|
e6c10f7
to
c73043c
Compare
8e086de
to
1bbde9c
Compare
eae6ef4
to
37359ee
Compare
5c91b06
to
d4af4d7
Compare
1daa1fa
to
1d41395
Compare
16aa81f
to
dffb466
Compare
Deprecate the built-in build process in favor of `dependsOn` Nx feature. Add support for libraries that doesn't require build process. BREAKING CHANGE: - `ngx-deploy-npm:install`: Added `--dist-folder-path` option as required. - `ngx-deploy-npm:install`: Drop the option `--projects`, now, each project needs to be specified independently using `--project`. - `ngx-deploy-npm:deploy`: `distFolderPath` option is now required. - `ngx-deploy-npm:deploy`: Remove options `noBuild` and `buildTarget`.
dffb466
to
faa263b
Compare
|
dianjuar
added a commit
that referenced
this pull request
Jan 16, 2024
Deprecate the built-in build process in favor of `dependsOn` Nx feature. Add support for libraries that doesn't require build process. BREAKING CHANGE: - `ngx-deploy-npm:install`: Added `--dist-folder-path` option as required. - `ngx-deploy-npm:install`: Drop the option `--projects`, now, each project needs to be specified independently using `--project`. - `ngx-deploy-npm:deploy`: `distFolderPath` option is now required. - `ngx-deploy-npm:deploy`: Remove options `noBuild` and `buildTarget`.
dianjuar
added a commit
that referenced
this pull request
Jan 18, 2024
Deprecate the built-in build process in favor of `dependsOn` Nx feature. Add support for libraries that doesn't require build process. BREAKING CHANGE: - `ngx-deploy-npm:install`: Added `--dist-folder-path` option as required. - `ngx-deploy-npm:install`: Drop the option `--projects`, now, each project needs to be specified independently using `--project`. - `ngx-deploy-npm:deploy`: `distFolderPath` option is now required. - `ngx-deploy-npm:deploy`: Remove options `noBuild` and `buildTarget`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
What is the current behavior?
Issue Number: #516 #553
What is the new behavior?
dependsOn
instead.deploy
executordistFolderPath
option is now required.buildTarget
option is now removed.noBuild
option is now removed.install
generatordistFolderPath
option is added and required to specify where the dist folder of the library.projects
option is removed in favor ofproject
. Now, we are allowed to configure a project at a time.distFolderPath
is required, it is difficult to provide multipledistFolderPath
when configuring multiple projects.Does this PR introduce a breaking change?
A migration script is provided for the next version to automate the required changes:
write-dist-folder-path-on-deploy-target-options
: Sets the distFolderPath option on the deploy target.distFolderPath
is now required.replace-buildtarget-for-depends-on
: Remove the optionbuildTarget
andnoBuild
from the deploy target. If the optionbuildTarget
was set, the migration will create a new target to build the library with the desired configuration and create adependsOn
on the deploy target to build the library using the just-created target.Other information