External profiles

[semanticfire]

Is your feature request related to a problem? Please describe. I would like to have 'external' profiles, creating a profile for my own documents requires me to have a profile in the official tree

Describe the solution you'd like ideally build.js takes a parameter to allow inclusion from a directory outside the repo

Describe any alternatives you've considered Fork the repo and merge the changes from the main line, although this works, it polutes the repository that only contains a profile.

Can you or your organization fund the work or help with development? I'm willing to invest some time in this, I would need some feedback if this is a desired path

[sidvishnoi]

ideally build.js takes a parameter to allow inclusion from a directory outside the repo

That might not be enough. How do you import() ReSpec core plugins outside of repo? It might be helpful if we can create a respec-dev package from where you can import core plugins (like import("respec-dev/core/inlines.js")) and run build & test scripts.

[semanticfire]

ideally build.js takes a parameter to allow inclusion from a directory outside the repo

That might not be enough. How do you import() ReSpec core plugins outside of repo? It might be helpful if we can create a respec-dev package from where you can import core plugins (like import("respec-dev/core/inlines.js")) and run build & test scripts.

I like the respec-dev idea. that would require a release process in some form on the main repo, but it would be a very clean solution

[sidvishnoi]

I can think of two ways:

• Create a new package.json during release via the tools/release.js script and release that package along with respec.
• Use a monorepo structure (like pnpm workspaces). Then respec can have respec-dev as a dev dependency.

The second feels cleaner and more robust, but it might break our current dev/test process. Will have to try it out. Can't give any timeline, but I can help with reviews if you send a PR.