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

Switch to a monorepo structure? #38

Open
jtpio opened this issue Feb 10, 2025 · 1 comment
Open

Switch to a monorepo structure? #38

jtpio opened this issue Feb 10, 2025 · 1 comment

Comments

@jtpio
Copy link
Member

jtpio commented Feb 10, 2025

For now having a simple directory structure which follows the extension template is enough.

However in the long run it may be more convenient to switch to a monorepo structure, and place all frontend packages under the packages folder.

Some ideas for new packages that could be developed in this repo:

@jtpio
Copy link
Member Author

jtpio commented Feb 10, 2025

Some ideas for new packages that could be developed in this repo:

But depending on whether these packages should be generic enough so they can be reused in Jupyter AI too, maybe they could also live in different repos (and different orgs). To be discussed.

@jtpio jtpio changed the title Switch to a monorepo structure Switch to a monorepo structure? Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant