-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to @xterm org on npm #4859
Comments
xterm-addon-image is excluded currently as there are some publishing issues. See xtermjs/xterm.js#4859
xterm-addon-image is excluded currently as there are some publishing issues. See xtermjs/xterm.js#4859
@Tyriar Wow, that already created quite a refactoring noise. Thx for getting it fixed this quickly. |
@jerch np, it was our tech debt week so conveniently timed 🙂 ended up being a pretty chunky VS Code PR too microsoft/vscode#197167 |
Would you please clarify how you are publishing the 5.4.0 betas during this transitional moment? For example:
For example: the timestamps indicate a more recent beta 14 publish than one numbered beta 37. I could have figured it out myself, but I didn't see git tags on the betas, so I'm not sure if there is an easy way for an outsider to track which hash each beta corresponds to. Let me know if I missed something. Thanks! |
@davidfiala |
What might be confusing here, is the fact that the 14 is actually newer than the 37. Have not looked up the publish script - my guess is, that the script simply started over for the Which means - anything in |
I deprecated xterm and xterm-headless. I don't think I can give it a custom message unfortunately |
In order to prevent problems like #4857 in the future let's move to scoped packages on npm. I don't consider this a breaking change as it needs a manual action to update anyway.
Plan:
@xterm/xterm
,@xterm/addon-search
, etc.<script>
elements here and on xtermjs.org (added by @jerch)The text was updated successfully, but these errors were encountered: