total rename thebox->snapshot

vercel · Apr 18, 2017 · cfab090 · cfab090
1 parent b755585
commit cfab090
Show file tree

Hide file tree

Showing 9 changed files with 209 additions and 209 deletions.
diff --git a/lib/README.md b/lib/README.md
@@ -144,23 +144,23 @@ During packaging process `pkg` collects project files and places
 them into executable. At run time the packaged application has
 internal virtual filesystem where all that files reside.
 
-Packaged VFS files have `/thebox/` prefix in their paths (or
-`C:\thebox\` in Windows). If you used `pkg /path/app.js` command line,
-then `__filename` value will be likely `/thebox/path/app.js`
-at run time. `__dirname` will be `/thebox/path` as well. Here is
+Packaged VFS files have `/snapshot/` prefix in their paths (or
+`C:\snapshot\` in Windows). If you used `pkg /path/app.js` command line,
+then `__filename` value will be likely `/snapshot/path/app.js`
+at run time. `__dirname` will be `/snapshot/path` as well. Here is
 the comparison table of path-related values:
 
-value                          | with `node`         | packaged                 | comments
--------------------------------|---------------------|--------------------------|-----------
-__filename                     | /project/app.js     | /thebox/project/app.js   |
-__dirname                      | /project            | /thebox/project          |
-process.cwd()                  | /project            | /deploy                  | suppose the app is called ...
-process.execPath               | /usr/bin/nodejs     | /deploy/app-x64          | `app-x64` and run in `/deploy`
-process.argv[0]                | /usr/bin/nodejs     | /deploy/app-x64          |
-process.argv[1]                | /project/app.js     | /deploy/app-x64          |
-process.pkg.entrypoint         | undefined           | /thebox/project/app.js   |
-process.pkg.defaultEntrypoint  | undefined           | /thebox/project/app.js   |
-require.main.filename          | /project/app.js     | /thebox/project/app.js   |
+value                          | with `node`         | packaged                   | comments
+-------------------------------|---------------------|----------------------------|-----------
+__filename                     | /project/app.js     | /snapshot/project/app.js   |
+__dirname                      | /project            | /snapshot/project          |
+process.cwd()                  | /project            | /deploy                    | suppose the app is called ...
+process.execPath               | /usr/bin/nodejs     | /deploy/app-x64            | `app-x64` and run in `/deploy`
+process.argv[0]                | /usr/bin/nodejs     | /deploy/app-x64            |
+process.argv[1]                | /project/app.js     | /deploy/app-x64            |
+process.pkg.entrypoint         | undefined           | /snapshot/project/app.js   |
+process.pkg.defaultEntrypoint  | undefined           | /snapshot/project/app.js   |
+require.main.filename          | /project/app.js     | /snapshot/project/app.js   |
 
 Hence in order to make use of the file collected at packaging
 time (pick up own JS plugin or serve an asset) you should take

diff --git a/lib/packer.js b/lib/packer.js
@@ -11,7 +11,7 @@ const STORE_STAT = common.STORE_STAT;
 
 const isDotJS = common.isDotJS;
 const isDotJSON = common.isDotJSON;
-const theboxify = common.theboxify;
+const snapshotify = common.snapshotify;
 
 const bootstrapText = fs.readFileSync(
   require.resolve('../prelude/bootstrap.js'), 'utf8'
@@ -67,7 +67,7 @@ function packer (opts, cb) {
     if (!first1) write(',');
     first1 = false;
 
-    write(JSON.stringify(theboxify(file, opts.slash)));
+    write(JSON.stringify(snapshotify(file, opts.slash)));
     write(':[\n');
 
     const record = records[file];
@@ -159,7 +159,7 @@ function packer (opts, cb) {
   opts.records.some(function (record) {
     if (record.entrypoint) {
 
-      write(JSON.stringify(theboxify(record.file, opts.slash)));
+      write(JSON.stringify(snapshotify(record.file, opts.slash)));
       return true;
 
     }