1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
Source: node-tmp
Section: javascript
Priority: optional
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>
Uploaders: Utkarsh Gupta <guptautkarsh2102@gmail.com>
Build-Depends: debhelper-compat (= 13)
, dh-sequence-nodejs
, mocha <!nocheck>
, node-rimraf <!nocheck>
Standards-Version: 4.6.1
Vcs-Browser: https://salsa.debian.org/js-team/node-tmp
Vcs-Git: https://salsa.debian.org/js-team/node-tmp.git
Homepage: https://github.com/raszi/node-tmp
Testsuite: autopkgtest-pkg-nodejs
Rules-Requires-Root: no
Package: node-tmp
Architecture: all
Depends: ${misc:Depends}
, node-rimraf
Provides: ${nodejs:Provides}
Description: Temporary file and directory creator for Node.js
The main difference between node-temp and node-tmp is that node-tmp more
aggressively checks for the existence of the newly created temporary file
and creates the new file with O_EXCL instead of simple O_CREAT | O_RDRW,
so it is safer.
.
The API is slightly different as well, Tmp does not yet provide
synchronous calls and all the parameters are optional.
.
Tmp uses crypto for determining random file names, or, when using templates,
a six letter random identifier. And just in case that you do not have that
much entropy left on your system, Tmp will fall back to pseudo random numbers.
.
You can set whether you want to remove the temporary file on process exit or
not, and the destination directory can also be set.
.
Node.js is an event-based server-side JavaScript engine.
|
