chore!: migrate to Nx workspace

[LayZeeDK]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Our CI workflow is broken and we are not publishing a partially Ivy-compiled bundle.

Issue Number: N/A

What is the new behavior?

We use Nrwl's Nx Cloud DTE workflow and we can publish a partially Ivy-compiled bundle.

Does this PR introduce a breaking change?

[x] Yes
[ ] No

• Require Angular 14.0
• Require RxJS 7.4

Other information

Merging from https://github.com/ngworker/lumberjack-next.

Closes #101, closes #84, closes #98

[NachoVazquez]

praise: Thanks for the effort so far it is looking great.

I left a couple of minor comments but the rest is starting to fit.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit c4aae29. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 8 targets

• nx affected --target=test --configuration=coverage --parallel=1 --max-workers=2
• nx affected --target=lint --configuration=report --parallel=2 --max-warnings=0
• nx affected --target=lint --configuration=report --parallel=2 --max-warnings=0
• nx affected --target=test --configuration=coverage --parallel=1 --max-workers=2
• nx affected --target=e2e --parallel=1
• nx affected --target=build --parallel=2
• nx-cloud record -- yarn nx format:check
• nx-cloud record -- yarn nx workspace-lint

---

Sent with 💌 from NxCloud.

[NachoVazquez]

🥇

[LayZeeDK]

Thank you for the review, @NachoVazquez ❤

I have shaved off 1 minute of CI time by including the e2e tests in parallel DTE agent tasks.

I also addressed the following issues.

• The custom build target was missing production and development configurations
• The build-package target wasn't cached by Nx
• The log payload wasn't covered by end-to-end tests

[LayZeeDK]

Hmm, the lint and test coverage report tasks aren't cached between the DTE jobs and the SonarCloud job.

[NachoVazquez]

Thank you for the review, @NachoVazquez ❤

I have shaved off 1 minute of CI time by including the e2e tests in parallel DTE agent tasks.

I also addressed the following issues.

• The custom build target was missing production and development configurations
• The build-package target wasn't cached by Nx
• The log payload wasn't covered by end-to-end tests

Amazing!!! Thank you!

[NachoVazquez]

Hmm, the lint and test coverage report tasks aren't cached between the DTE jobs and the SonarCloud job.

Oh, nice observation. 🤔

[LayZeeDK]

Seems like the Nx agents aren't picking up the NX_CLOUD_ACCESS_TOKEN GitHub secret. We probably need to pass them to the reusable workflows.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

98.0% Coverage
0.0% Duplication

[LayZeeDK]

Success! 🙌

[NachoVazquez]

We did it!!!!