Skip to content
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

Add more documentation for how to work with Deno Workspace #700

Open
halvardssm opened this issue Aug 10, 2024 · 0 comments
Open

Add more documentation for how to work with Deno Workspace #700

halvardssm opened this issue Aug 10, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@halvardssm
Copy link

halvardssm commented Aug 10, 2024

As the title suggests, I was hoping it would be possible to get some more documentation around the use of deno workspaces?

The current documentation is lacking the following:

  • How to import code from other workspaces
    • Say there is a ModuleA and ModuleB in a Deno workspace, how can I import MethodA from ModuleA in ModuleB?
    • How will this translate when deploying the modules to JSR?
  • How to run deploy for just one of the modules, or a selected set of modules
  • Recommended way of bumping module versions
    • Maybe a subcommand could be introduced that works in the similar way as the script for bumping in std?
    • Alternatively, publish the script for easy usage in other projects that wants to follow the best practices?
  • Recommended way to deploy test versions (release candidates) of selected modules (e.g. 0.0.0-rc.1)
@dsherret dsherret transferred this issue from denoland/deno Aug 10, 2024
@thisisjofrank thisisjofrank added the documentation Improvements or additions to documentation label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants