Repository navigation
chore(tests): add verdaccio to package.json - #202
Conversation
99c2345 to
1447b4a
Compare
X-Guardian
left a comment
There was a problem hiding this comment.
I've actually already included this change in #170, but took it further and re-wrote the local-registry.sh script in javascript and enhanced the verdaccio process handling. Happy to split this out, as #170 is getting very large.
How about we include the local-registry change from #170 in this PR? I have refined it to also resolve #199.
ad3b51f to
0c2ea8c
Compare
@X-Guardian Done. |
0c2ea8c to
afc3e5d
Compare
|
seems tests are still failing after rebase SYNTH_HCL_OUTPUT: false
...
Cleaning storage dir (/__w/cdk-terrain/cdk-terrain/test/storage)..
Verdaccio Registry log file: /tmp/verdaccio-OH0GZw/verdaccio.log
Waiting for local Registry to start
Verdaccio exited before becoming ready (code=127, signal=null).
--- verdaccio log (tail) ---
sh: 1: verdaccio: not found
----------------------------
Error: Process completed with exit code 1. |
@X-Guardian any ideas why we'd see this only for some tests? |
|
We need to install the test dependencies as part of the examples integration test workflow. See https://github.com/open-constructs/cdk-terrain/pull/170/changes#diff-8906835152921ef903f55779586f3a092362f65fca98df94d71801cf974ec95bR141-R142 |
afc3e5d to
5780662
Compare
Thanks, updated. Let's see if that's enough to fix all the errors. 🤞 |
|
@gabegorelick, it would be great to get this merged if you could resolve the conflicts. |
We were installing it via npx, which means its dependencies weren't pinned. In the age of supply chain attacks, that's not great.
5780662 to
ef38063
Compare
Done. Conflicts are resolved. |
## 0.23.3 ### chore - chore(gha): run integration tests on Depot runners [\#238](#238) - chore(deps): bump typescript to 5.9.3 across the repo [\#231](#231) - chore: Upgrade jsii [\#223](#223) - chore: Revise README links to documentation and language support [\#221](#221) - chore: Pin node version to 22.22.2 via .nvmrc [\#212](#212) - chore: Add gradle cache to the examples and integration CI workflows [\#211](#211) - chore: Add PR workflow concurrency group and CI Label Filter job [\#204](#204) - chore(tests): add verdaccio to package.json [\#202](#202) - chore(tests): don't require other language builds [\#201](#201) - chore(tests): Ensure we terminate Verdaccio [\#199](#199) - chore: rewrite https://cdk.tf links [\#197](#197) - chore: Update examples help files [\#194](#194) ### feat - feat: faster JSON stringify [\#224](#224) - feat(lib): allow disabling creation stacks [\#215](#215) ### fix - fix(lib): surface stderr/stdout on exec() failures via toString() [\#207](#207) --------- Co-authored-by: so0k <vincent.drl@gmail.com> Co-authored-by: sakul-learning <lucas@sheesh.host>
We currently run verdaccio by spawning an `npm run` process. But since `local-registry` is a JS file now (open-constructs#202), we can just call verdaccio's JS API directly. See open-constructs#202 (comment)
We currently run verdaccio by spawning an `npm run` process. But since `local-registry` is a JS file now (open-constructs#202), we can just call verdaccio's JS API directly. See open-constructs#202 (comment)
We currently run verdaccio by spawning an `npm run` process. But since `local-registry` is a JS file now (#202), we can just call verdaccio's JS API directly. See #202 (comment) <!-- Unless this is a very simple 1-line-of-code change, please create a new issue describing the change you're proposing first, then link to it from this PR. Read more about our process in our contributing guide: https://github.com/open-constructs/cdk-terrain/blob/main/CONTRIBUTING.md --> ### Related issue Fixes # <!-- INSERT ISSUE NUMBER --> ### Description In plain English, describe your approach to addressing the issue linked above. For example, if you made a particular design decision, let us know why you chose this path instead of another solution. ### Checklist - [x] I have updated the PR title to match [CDKTN's style guide](https://github.com/open-constructs/cdk-terrain/blob/main/CONTRIBUTING.md#pull-requests-1) - [x] I have run the linter on my code locally - [x] I have performed a self-review of my code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the [documentation](https://github.com/open-constructs/cdk-terrain-docs/tree/main/content) if applicable - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works if applicable - [x] New and existing unit tests pass locally with my changes <!-- If this is still a work in progress, feel free to open a draft PR until you're able to check off all the items on the list above -->
|
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
We were installing it via npx, which means its dependencies weren't pinned. In the age of supply chain attacks, that's not great.
Related issue
Fixes #
Description
Add
verdacciototest/package.jsonChecklist