Skip to content

README for users of this tool#53

Draft
paulgries wants to merge 2 commits into
mainfrom
cave-readme
Draft

README for users of this tool#53
paulgries wants to merge 2 commits into
mainfrom
cave-readme

Conversation

@paulgries
Copy link
Copy Markdown
Collaborator

Proposed Changes

A README.md file with installation, setup, and execution instructions for people who want to run this tool.
Closes #20.)

...

Screenshots of your changes (if applicable)

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue)
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📚 Documentation update (change that only updates documentation) X
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

  • I have performed a self-review of my changes.
    • Check that all changed files included in this pull request are intentional changes.
    • Check that all changes are relevant to the purpose of this pull request, as described above.
  • I have added tests for my changes, if applicable.
    • This is required for all bug fixes and new features.
  • I have updated the project documentation, if applicable.
    • This is required for new features.
  • I have updated the project Changelog (this is required for all changes).

After opening your pull request:

  • I have verified that the CI tests have passed.
  • I have requested a review from a project maintainer, and a fellow student.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

@paulgries paulgries marked this pull request as draft March 12, 2026 16:25
Start the development server:

```bash
cave view <filepath>
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This works with the --console flag (stdout) but results in this error otherwise:

"npm error Missing script: "dev"

cd clean-architecture-visualizer
npm install
npm run build
npm link
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried following this and it fails at the npm link step:

Image

@matt-dahlgren is this the expected behavior right now?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it is.

npm link is used for local development (so that we can test our cli locally without needing to publish/fully download a package) as seen here in the documentation.

I will be addressing how to properly download cave on my next task in documentation. But we are going to deploy it similarly as MemoryViz is deployed.

If you see here it is an npm download of the repo itself. This change will include a small addition of a package.json to the outermost layer of this project. But it will allow for faster bug changes.

TLDR: npm link is used in development, it is not useable in production as it is looking for a local directory to build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Write installation instructions

4 participants