Project's xpacks folder hierarchy #210
-
Hi, The project's /xpacks folder hierarchy isn't similar if the project has xPacks from only one "category" (for instance, 3rd party source xPacks) or has xPacks from several "categories" (for instance, 3rd party source xPacks and xPack Binary Development Tools). This is pitty if we use the relative path of a xPack file, for instance to use an extension of the Doxygen awesome css. The user guide of this project indicates:
The doxygen-awesome-darkmode-toggle.js is in the xpack-3rd-party-doxygen-awesome-css folder. Have you any idea to solve it? May be an option of In advance, thank you. Hierarchies examplesHierarchy with only one "category":
Hierarchy with several "categories":
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Hi @jsineau-asulab, I'm not sure I understand your questions. Are you using the latest xpm and your project is configured with a recent The strategy used for creating sub-folders changed at a certain point, and now it should look like:
in other words, the npm |
Beta Was this translation helpful? Give feedback.
-
As an example of using the |
Beta Was this translation helpful? Give feedback.
-
Hi @ilg-ul, I understand now. I started my project with a copy/paste of the package.json from the doxygen-awesome-css-xpack. Within this package.json the Therefore, I shall update this parameter from Do you want that I update your project? 🙏 Thank you Liviu and my apologies for my english |
Beta Was this translation helpful? Give feedback.
Hi @jsineau-asulab,
I'm not sure I understand your questions.
Are you using the latest xpm and your project is configured with a recent
minimumXpmRequired
in yourpackage.json
?The strategy used for creating sub-folders changed at a certain point, and now it should look like:
in other words, the npm
@scope
is preserved and the name is not linearised.