wide-midnight-78598
04/27/2023, 8:34 PMcurved-television-6568
04/27/2023, 8:35 PMbitter-ability-32190
04/27/2023, 8:37 PMtwine
plugin for publishing?curved-television-6568
04/27/2023, 8:37 PMbitter-ability-32190
04/27/2023, 8:37 PMcurved-television-6568
04/27/2023, 8:38 PMenough-analyst-54434
04/27/2023, 8:39 PMwide-midnight-78598
04/27/2023, 8:39 PMenough-analyst-54434
04/27/2023, 8:40 PMwide-midnight-78598
04/27/2023, 8:42 PMenough-analyst-54434
04/27/2023, 8:43 PMwide-midnight-78598
04/27/2023, 8:43 PMimport { Dialog } from "@robotpajamas/svelte-headlessui"
I could easily re-publish this to another organization, or access files by @robotpajamas/svelte-headlessui/Dialog
So, if I have something like:
pip install robotpajamas.pants.scie
Does that mean, if I want to import using the same structure, I necessarily need to keep my source files in that same module structure too?
Or is there some alias concept I can apply?
So like, root/src/scie
somehow automagically becomes robotpajamas.pants.scie
?pantsbuild.pants
imports at <http://pants.xyz|pants.xyz>
)enough-analyst-54434
05/21/2023, 2:53 PM__pex__.
psuedo-package prefix to all 3rdparty code.wide-midnight-78598
05/21/2023, 2:55 PMenough-analyst-54434
05/21/2023, 2:58 PMwide-midnight-78598
05/21/2023, 3:00 PMpip install abc.xzy.scie
to be how the end user also consumes the plugin. So from the user's perspective, the experience is consistent.
I was just mildly hoping to not have to also make my source code structure align to the same tedious namespacing convention.enough-analyst-54434
05/21/2023, 3:02 PMwide-midnight-78598
05/21/2023, 3:04 PMenough-analyst-54434
05/21/2023, 3:04 PMwide-midnight-78598
05/21/2023, 3:04 PM