npm package @openscd/core reset
From @trusz
We would like reset and restart the @openscd/core package on npm. We want to deploy the new core functionalities. It is drastically different and I think nobody really uses it I would like to make sure.
So if you have anything against it please let me know until 11.04 (Friday) Thank you!
OK I'll bite.
I use this in many plugins, as does @JakobVogelsang and also @ca-d in a few. Do we have a drop-in replacement?
Here is a small massaged list of mentions from my filesystem, using rg -l '@openscd/open-scd-core' --glob package.json
ca-d/oscd-designer
ca-d/oscd-open
ca-d/oscd-save
danyill/oscd-automatic-backup
danyill/oscd-communications-export
danyill/oscd-description
danyill/oscd-import-ieds
danyill/oscd-import-templates
danyill/oscd-network-config
danyill/oscd-remove-ieds
danyill/oscd-replace-ieds
danyill/oscd-save-as
danyill/oscd-stencil
danyill/oscd-subscriber-lb-nr
danyill/oscd-subscriber-lb-sel
danyill/oscd-subscriber-lb-siemens
danyill/oscd-tp-multicast-naming
danyill/oscd-network-data
danyill/oscd-subscriber-later-binding
danyill/oscd-supervision
OpenEnergyTools/oscd-action-translate
OpenEnergyTools/scl-communication-editor
OpenEnergyTools/scl-lib
OpenEnergyTools/scl-substation-editor
OpenEnergyTools/scl-validating
Why do we need to break compatibility? Can't we at least leave what is published available even if we clear out the repository?
I'm also very often using a import '@openscd/open-scd-core/open-scd.js' into a demo/index.html page.
I think I could likely replace in my projects with @openenergytools/open-scd-core
However this didn't work for import '@openscd/open-scd-core/open-scd.js' in demo/index.html and I am awaiting for a new release of core to do this. What I did previously was based on a gh-pages import 'https://openscd.github.io/open-scd-core/open-scd.js'; which would potentially also break in a clean-out.
I think with a new release of @openenergytools/open-scd-core (which included https://github.com/OpenEnergyTools/open-scd-core/issues/20) and a little time and I could probably remove this dependency.
Thank you for gathering everything. I've undo the deprecation message, but we might want to do it again for the current version.
My proposal: We have been always on 0.1.x so I think we can upgrade to 0.2.x with the new idea, then if we reach the first stable version just jump onto 1.0.0 so you can keep using the 0.1.x versions.
Would that work for you?
Yes that sounds fine
On Thu, 10 Apr 2025, 23:33 Tamás Russ, @.***> wrote:
Thank you for gathering everything. I've undo the deprecation message, but we might want to do it again for the current version.
My proposal: We have been always on 0.1.x so I think we can upgrade to 0.2.x with the new idea, then if we reach the first stable version just jump onto 1.0.0 so you can keep using the 0.1.x versions.
Would that work for you?
— Reply to this email directly, view it on GitHub https://github.com/openscd/open-scd/issues/1659#issuecomment-2793062390, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFEXX43O4WPWLWCV6DZ5N32YZXLPAVCNFSM6AAAAAB23ENZ52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJTGA3DEMZZGA . You are receiving this because you commented.Message ID: @.***> trusz left a comment (openscd/open-scd#1659) https://github.com/openscd/open-scd/issues/1659#issuecomment-2793062390
Thank you for gathering everything. I've undo the deprecation message, but we might want to do it again for the current version.
My proposal: We have been always on 0.1.x so I think we can upgrade to 0.2.x with the new idea, then if we reach the first stable version just jump onto 1.0.0 so you can keep using the 0.1.x versions.
Would that work for you?
— Reply to this email directly, view it on GitHub https://github.com/openscd/open-scd/issues/1659#issuecomment-2793062390, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFEXX43O4WPWLWCV6DZ5N32YZXLPAVCNFSM6AAAAAB23ENZ52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJTGA3DEMZZGA . You are receiving this because you commented.Message ID: @.***>
For avoidance of doubt I'm not using @openscd/core only @openscd/open-scd-core and I'm not concerned about @openscd/core which can be reset.
This package should be renamed https://github.com/openscd/core/tree/main It uses the same package.json name as https://github.com/openscd/open-scd/tree/main/packages/core (which is the one published on npm and that is concerned by the issue)
There is 5 core packages linked to open scd :
- Open energy tools
- Alliander
- Open scd -> plugins + rendering | rendering
There are still discussion about the renaming on this core packages. The core term is confusing for everyone.
We are waiting @trusz intervention during a next meeting to clarify things up.