Piotr Osiewicz
84f4d2630f
This partially reverts https://github.com/zed-industries/zed/pull/3324 We will still blank out user/global config when running managed NPM, to keep to the spirit of #3324 (which was made at the time we did not allow user-provided NPM builds - the intent of the change was to make the behavior of NPM as consistent as possible). I tested this change by: 1. Setting up a custom NPM registry via Versaccio 2. Adding this new registry to my .npmrc 3. Mirroring `vscode-langservers-extracted` to it 4. Blocking access to `registry.npmjs.org` 5. Opening up settings.json file in Zed Nightly - Verifying that language server update fails for it 6. Opening up Zed Dev build of this branch - Confirming that language server update check goes through for it Closes #19806 Closes #20749 Closes #9422 Release Notes: - User and global .npmrc configuration is now respected when running user-provided NPM binary (which also happens automatically when `npm` from PATH is newer than 18.0.0)
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.