Jupyterlite-terminal

Latest version: v0.1.1

Safety actively analyzes 666166 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

0.1.1

([Full Changelog](https://github.com/jupyterlite/terminal/compare/v0.1.0...f730b658ac11ee7299f697bb81781e2746c83655))

Enhancements made

- Remove WebWorker code that is now in cockle [21](https://github.com/jupyterlite/terminal/pull/21) ([ianthomas23](https://github.com/ianthomas23))
- Replace postMessage from webworker with comlink callback [16](https://github.com/jupyterlite/terminal/pull/16) ([ianthomas23](https://github.com/ianthomas23))
- Use WASM commands running in webworker [15](https://github.com/jupyterlite/terminal/pull/15) ([ianthomas23](https://github.com/ianthomas23))

Bugs fixed

- Fix listing of terminals [11](https://github.com/jupyterlite/terminal/pull/11) ([jtpio](https://github.com/jtpio))

Maintenance and upkeep improvements

- Update jupyterlite to 0.4.0 and cockle to 0.0.5 [18](https://github.com/jupyterlite/terminal/pull/18) ([ianthomas23](https://github.com/ianthomas23))
- Support JupyterLite 0.4.0 packages [14](https://github.com/jupyterlite/terminal/pull/14) ([jtpio](https://github.com/jtpio))

Documentation improvements

- Add JupyterLite badge to the README [10](https://github.com/jupyterlite/terminal/pull/10) ([jtpio](https://github.com/jtpio))
- Add workflow for deploying a demo to GitHub Pages [9](https://github.com/jupyterlite/terminal/pull/9) ([jtpio](https://github.com/jtpio))

Contributors to this release

([GitHub contributors page for this release](https://github.com/jupyterlite/terminal/graphs/contributors?from=2024-05-29&to=2024-09-16&type=c))

[ianthomas23](https://github.com/search?q=repo%3Ajupyterlite%2Fterminal+involves%3Aianthomas23+updated%3A2024-05-29..2024-09-16&type=Issues) | [jtpio](https://github.com/search?q=repo%3Ajupyterlite%2Fterminal+involves%3Ajtpio+updated%3A2024-05-29..2024-09-16&type=Issues)

<!-- <END NEW CHANGELOG ENTRY> -->

0.1.0

([Full Changelog](https://github.com/jupyterlite/terminal/compare/1076c3fb09302a306d7084f72d2fb58ead8adc84...b3ae8d8409eaa8d883ad52eb829016951001790b))

Enhancements made

- Add missing dependencies and handling of terminal clients [2](https://github.com/jupyterlite/terminal/pull/2) ([jtpio](https://github.com/jtpio))
- Skip the browser check for now [1](https://github.com/jupyterlite/terminal/pull/1) ([jtpio](https://github.com/jtpio))

Maintenance and upkeep improvements

- Reset version for initial release [8](https://github.com/jupyterlite/terminal/pull/8) ([jtpio](https://github.com/jtpio))
- Rename package to `jupyterlite/terminal` [7](https://github.com/jupyterlite/terminal/pull/7) ([jtpio](https://github.com/jtpio))

Contributors to this release

([GitHub contributors page for this release](https://github.com/jupyterlite/terminal/graphs/contributors?from=2024-05-16&to=2024-05-29&type=c))

[jtpio](https://github.com/search?q=repo%3Ajupyterlite%2Fterminal+involves%3Ajtpio+updated%3A2024-05-16..2024-05-29&type=Issues)


Making a new release of jupyterlite_terminal

The extension can be published to `PyPI` and `npm` manually or using the [Jupyter Releaser](https://github.com/jupyter-server/jupyter_releaser).

Manual release

Python package

This extension can be distributed as Python packages. All of the Python
packaging instructions are in the `pyproject.toml` file to wrap your extension in a
Python package. Before generating a package, you first need to install some tools:

bash
pip install build twine hatch


Bump the version using `hatch`. By default this will create a tag.
See the docs on [hatch-nodejs-version](https://github.com/agoose77/hatch-nodejs-version#semver) for details.

bash
hatch version <new-version>


Make sure to clean up all the development files before building the package:

bash
jlpm clean:all


You could also clean up the local git repository:

bash
git clean -dfX


To create a Python source package (`.tar.gz`) and the binary package (`.whl`) in the `dist/` directory, do:

bash
python -m build


> `python setup.py sdist bdist_wheel` is deprecated and will not work for this package.

Then to upload the package to PyPI, do:

bash
twine upload dist/*


NPM package

To publish the frontend part of the extension as a NPM package, do:

bash
npm login
npm publish --access public


Automated releases with the Jupyter Releaser

The extension repository should already be compatible with the Jupyter Releaser. But
the GitHub repository and the package managers need to be properly set up. Please
follow the instructions of the Jupyter Releaser [checklist](https://jupyter-releaser.readthedocs.io/en/latest/how_to_guides/convert_repo_from_repo.html).

Here is a summary of the steps to cut a new release:

- Go to the Actions panel
- Run the "Step 1: Prep Release" workflow
- Check the draft changelog
- Run the "Step 2: Publish Release" workflow

> [!NOTE]
> Check out the [workflow documentation](https://jupyter-releaser.readthedocs.io/en/latest/get_started/making_release_from_repo.html)
> for more information.

Publishing to `conda-forge`

If the package is not on conda forge yet, check the documentation to learn how to add it: https://conda-forge.org/docs/maintainer/adding_pkgs.html

Otherwise a bot should pick up the new version publish to PyPI, and open a new PR on the feedstock repository automatically.

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.