Release timings

[vethan]

Draft orders being merged in to Nocto but not released makes me wonder is this going to be maintained/kept up-to-date?

[radoslaw-sz]

hi @vethan - sorry I missed it. New version has been released (0.2.1).

PS. No promises about keeping the nocto in sync often with Medusa to be honest. This concept unfortunatly did not get big popularity so far... :(

[vethan]

Well we at Wildkind would really like to use it! Happy to support the project as regular contributors if we can get an automated release process

[vethan]

@radoslaw-sz any interest in that?

[radoslaw-sz]

hi @vethan - could you please drop the email at labs@rsoftcon.com? We will try to find some solution :)

[docloulou]

Hi, i'm waiting auto sync to start using your wonderfull work @radoslaw-sz any news on this ?
Thanks ;)

[docloulou]

Is this just an upstream sync from the Medusa Git repository +a package.json update, or does it require some tweaking for each Medusa dashboard update?

[radoslaw-sz]

hi @docloulou - unforutnatley, due to major changes in the core of the medusa dashboard, auto-sync is not possible. There will be always some manual work to do. Actually, right now is it even easier because there is no many NoctoSlots introduced into the code. If there will be more and more, then merging of upstream will be harder and harder.
But this is a reality - Nocto has been created for people/companies which need one base of the code and publish a lot of projects just replacing NoctoSlots. I think then such investment of merging is acceptable.

[docloulou]

Basically, I haven’t dug deeply into the code yet, but would it be possible to rsync the @dashboard part from the Medusa repo and then run a codemod script to target (using a JSON list maintained alongside the script) the specific components we want to replace with the Noctoslot ones? (In nocto/src)

Would that be enough, or are there any subtleties I’m missing?

[radoslaw-sz]

Basically, I haven’t dug deeply into the code yet, but would it be possible to rsync the @dashboard part from the Medusa repo and then run a codemod script to target (using a JSON list maintained alongside the script) the specific components we want to replace with the Noctoslot ones? (In nocto/src)

Would that be enough, or are there any subtleties I’m missing?

Hard to say - I have a feeling that full automation is not possible, but I might be wrong. Routing and sidebar implementation is different in Nocto (to achieve RBAC properly), so if something is being changed in routing (like adding new routes) then it shall be migrated to Nocto implementation.
Maybe using AI would be possible to have it automated - no clue to be honest. I never tried something similar before and due to not so high interest in Nocto - my time is limited for this project.

[docloulou]

Hi @radoslaw-sz,
I've developed a bash script to automate the Medusa Dashboard upgrade process in Nocto while preserving our customizations. This script greatly simplifies the upgrade process and reduces the risk of errors.

The script packages/nocto/scripts/upgrade-medusa.sh automatically performs the following operations:
✅ Automated Operations

• Download: Automatically fetches the latest version of @medusajs/dashboard from npm
• Smart Detection: Scans the project to identify all files containing components
• Backup: Creates backups of all custom files before any modification
• Source Code Update: Extracts the new version into packages/nocto/src while excluding:
  - The plugin-system/ and plugins/ directories
  - Custom configuration files (utils.ts, get-route.map.tsx, main.tsx, app.tsx)
  - All files containing <NoctoSlot ...> (automatic detection)
• Restoration: Automatically restores all custom files
• Dependency Update: Automatically updates all @medusajs/** versions in package.json
  - @medusajs/ui: uses its own latest version
  - Other packages: aligned with the dashboard version

⚠️ Manual Operations Required
After each script execution, you must manually verify:

1. Files with NoctoSlot
   The script automatically lists all files containing that were preserved. For each listed file, you need to:

• Compare with the new Medusa version
• Check if any props have changed
• Verify if new hooks or contexts are required
• Ensure imports are still valid
• Test functionality in production

Currently detected files (approx. 11 files):

• routes/customers/customer-list/customer-list.tsx
• routes/products/product-list/product-list.tsx
• routes/orders/order-list/order-list.tsx
• routes/orders/order-detail/order-detail.tsx
  ....

2. Custom Configuration Files
   These files are always preserved but may require adjustments:

• dashboard-app/routes/utils.ts - Custom routing logic
• dashboard-app/routes/get-route.map.tsx - Route mapping
• main.tsx - Custom entry point
• app.tsx - Application configuration

[docloulou]

BONUS: i added a typescript check on excluded file to be sure there are no issues after upgrading : ./upgrade-medusa.sh --check

[radoslaw-sz]

hi @docloulou - that's incredible good work! Let me test it in the next days and if everything will work well, then I will more than happy if you can create pull request with this script. README update is also welcome, but I can handle it by myself. I will then also include this information in noctojs.com

[docloulou]

hi @docloulou - that's incredible good work! Let me test it in the next days and if everything will work well, then I will more than happy if you can create pull request with this script. README update is also welcome, but I can handle it by myself. I will then also include this information in noctojs.com

Just notice I forgot the draft order plugin sync ... will update the script for that.
I just want you to check if excluded files are fine, you know better nocto architecture than me ;)
For README you mean the main git readme ? The purpose is to explain how to update for fork or dev ?

Moreover, too bad the project is not enough popular, Medusa community is growing just be patient

[radoslaw-sz]

hi @docloulou ,
unfortunately due to holiday season it will take some more days to find a time to take a look at it.

PS. Just let you know that Medusa team core is working on RBAC in Medusa (if this is something which you are happy have in nocto)

[radoslaw-sz]

I checked the script and here are my comments:

• we need to preserve also packages/nocto/src/providers/providers.tsx. The reason is that normally there is a QueryClientProvider but we are using higher in the tree due to RBAC functionality.
• we need to preserve packages/nocto/src/routes/products/product-detail/constants.ts. This is very unfortunate, but I couldn't solve it in the reasonable time to support getLinkedFields function (it was related to the built mechanism of nocto). It means that PRODUT_DETAILS_FIELDS is just a list of hardcoded fields, without getLinkedFields.
• we need to preserve packages/nocto/src/components/layout/main-layout /main-layout - this file is responsible for building the sidebar
• we need to preserve packages/nocto/src/index.ts - this is entry point for Nocto

Last but not least - every change under /routes direcotry needs special attention. This is due to the fact taht new routes added there needs to be migrated to existing plugin (e.g. new route under category needs to be added to category plugin) or totally new routes (like translations) need to be migrated to the totally new plugin.

Thanks to your script we are closer to have it automated, but still - we need to analyze and learn what can be automated more.