毕设项目：后端springboot + mybatis + jpa，前端vue实现的简易网盘系统.zip

<p align="center"> <a href="https://nodejs.org/"> <img alt="Node.js" src="https://nodejs.org/static/images/logo-light.svg" width="400" /> </a> </p> Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. For more information on using Node.js, see the [Node.js Website][]. The Node.js project is supported by the [Node.js Foundation](https://nodejs.org/en/foundation/). Contributions, policies, and releases are managed under an [open governance model](./GOVERNANCE.md). **This project is bound by a [Code of Conduct][].** # Table of Contents * [Support](#support) * [Release Types](#release-types) * [Download](#download) * [Current and LTS Releases](#current-and-lts-releases) * [Nightly Releases](#nightly-releases) * [API Documentation](#api-documentation) * [Verifying Binaries](#verifying-binaries) * [Building Node.js](#building-nodejs) * [Security](#security) * [Current Project Team Members](#current-project-team-members) * [TSC (Technical Steering Committee)](#tsc-technical-steering-committee) * [Collaborators](#collaborators) * [Release Team](#release-team) * [Contributing to Node.js](#contributing-to-nodejs) ## Support Node.js contributors have limited availability to address general support questions. Please make sure you are using a [currently-supported version of Node.js](https://github.com/nodejs/Release#release-schedule). When looking for support, please first search for your question in these venues: * [Node.js Website][] * [Node.js Help][] * [Open or closed issues in the Node.js GitHub organization](https://github.com/issues?utf8=%E2%9C%93&q=sort%3Aupdated-desc+org%3Anodejs+is%3Aissue) If you didn't find an answer in one of the official resources above, you can search these unofficial resources: * [Questions tagged 'node.js' on StackOverflow][] * [#node.js channel on chat.freenode.net][]. See <http://nodeirc.info/> for more information. * [Node.js Discord Community](https://discordapp.com/invite/v7rrPdE) * [Node.js Slack Community](https://node-js.slack.com/): Visit [nodeslackers.com](http://www.nodeslackers.com/) to register. GitHub issues are meant for tracking enhancements and bugs, not general support. Remember, libre != gratis; the open source license grants you the freedom to use and modify, but not commitments of other people's time. Please be respectful, and set your expectations accordingly. ## Release Types The Node.js project maintains multiple types of releases: * **Current**: Released from active development branches of this repository, versioned by [SemVer](https://semver.org) and signed by a member of the [Release Team](#release-team). Code for Current releases is organized in this repository by major version number. For example: [v4.x](https://github.com/nodejs/node/tree/v4.x). The major version number of Current releases will increment every 6 months allowing for breaking changes to be introduced. This happens in April and October every year. Current release lines beginning in October each year have a maximum support life of 8 months. Current release lines beginning in April each year will convert to LTS (see below) after 6 months and receive further support for 30 months. * **LTS**: Releases that receive Long-term Support, with a focus on stability and security. Every second Current release line (major version) will become an LTS line and receive 18 months of _Active LTS_ support and a further 12 months of _Maintenance_. LTS release lines are given alphabetically ordered codenames, beginning with v4 Argon. LTS releases are less frequent and will attempt to maintain consistent major and minor version numbers, only incrementing patch version numbers. There are no breaking changes or feature additions, except in some special circumstances. * **Nightly**: Versions of code in this repository on the current Current branch, automatically built every 24-hours where changes exist. Use with caution. More information can be found in the [LTS README](https://github.com/nodejs/LTS/). ### Download Binaries, installers, and source tarballs are available at <https://nodejs.org>. #### Current and LTS Releases **Current** and **LTS** releases are available at <https://nodejs.org/download/release/>, listed under their version strings. The [latest](https://nodejs.org/download/release/latest/) directory is an alias for the latest Current release. The latest LTS release from an LTS line is available in the form: latest-_codename_. For example: <https://nodejs.org/download/release/latest-argon>. #### Nightly Releases **Nightly** builds are available at <https://nodejs.org/download/nightly/>, listed under their version string which includes their date (in UTC time) and the commit SHA at the HEAD of the release. #### API Documentation **API documentation** is available in each release and nightly directory under _docs_. <https://nodejs.org/api/> points to the API documentation of the latest stable version. ### Verifying Binaries Current, LTS, and Nightly download directories all contain a SHASUMS256.txt file that lists the SHA checksums for each file available for download. The SHASUMS256.txt can be downloaded using `curl`. ```console $ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt ``` To check that a downloaded file matches the checksum, run it through `sha256sum` with a command such as: ```console $ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c - ``` Current and LTS releases (but not Nightlies) also have the GPG detached signature of SHASUMS256.txt available as SHASUMS256.txt.sig. You can use `gpg` to verify that SHASUMS256.txt has not been tampered with. To verify SHASUMS256.txt has not been altered, you will first need to import all of the GPG keys of individuals authorized to create releases. They are listed at the bottom of this README under [Release Team](#release-team). Use a command such as this to import the keys: ```console $ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D ``` See the bottom of this README for a full script to import active release keys. Next, download the SHASUMS256.txt.sig for the release: ```console $ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig ``` After downloading the appropriate SHASUMS256.txt and SHASUMS256.txt.sig files, you can then use `gpg --verify SHASUMS256.txt.sig SHASUMS256.txt` to verify that the file has been signed by an authorized member of the Node.js team. Once verified, use the SHASUMS256.txt file to get the checksum for the binary verification command above. ## Building Node.js See [BUILDING.md](BUILDING.md) for instructions on how to build Node.js from source. The document also contains a list of officially supported platforms. ## Security Security flaws in Node.js should be reported by emailing security@nodejs.org. Please do not disclose security bugs publicly until they have been handled by the security team. Your email will be acknowledged within 24 hours, and you will receive a more detailed response to your email within 48 hours indicating the next steps in handling your report. There are no hard and fast rules to determine if a bug is worth reporting as a security issue. The general rule is an issue worth reporting should allow an attacker to compromise the confidentiality, integrity, or availability of the Node.js application or its system for which the attacker does not already have the capability. To illustrate the point, here are some examples of past issues and what the Security Response Team thinks of them. When in doubt, however, please do send us a report nonetheless. ### Public disclosure preferred - [#14519](https://github.com/nodejs/node/issues/14519): _Internal domain function can be used to cause segfaults_. Causing program termination using either the public JavaScript APIs or the private bindings layer APIs requires the ability to execute arbitra