@vercel/python 2.0.6-canary.7 → 2.1.2-canary.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +4 -0
- package/package.json +2 -2
package/dist/index.js
CHANGED
|
@@ -3797,6 +3797,10 @@ async function installRequirement({ pythonPath, pipPath, dependency, version, wo
|
|
|
3797
3797
|
}
|
|
3798
3798
|
exports.installRequirement = installRequirement;
|
|
3799
3799
|
async function installRequirementsFile({ pythonPath, pipPath, filePath, workPath, meta, args = [], }) {
|
|
3800
|
+
// The Vercel platform already handles `requirements.txt` for frontend projects,
|
|
3801
|
+
// but the installation logic there is different, because it seems to install all
|
|
3802
|
+
// of the dependencies globally, whereas, for this Runtime, we want it to happen only
|
|
3803
|
+
// locally, so we'll run a separate installation.
|
|
3800
3804
|
if (meta.isDev &&
|
|
3801
3805
|
(await areRequirementsInstalled(pythonPath, filePath, workPath))) {
|
|
3802
3806
|
build_utils_1.debug(`Skipping requirements file installation, already installed`);
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vercel/python",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.1.2-canary.2",
|
|
4
4
|
"main": "./dist/index.js",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"homepage": "https://vercel.com/docs/runtimes#official-runtimes/python",
|
|
@@ -24,5 +24,5 @@
|
|
|
24
24
|
"execa": "^1.0.0",
|
|
25
25
|
"typescript": "4.3.4"
|
|
26
26
|
},
|
|
27
|
-
"gitHead": "
|
|
27
|
+
"gitHead": "d3ef240f6e01fff3d11d0499c9aaf892968748e3"
|
|
28
28
|
}
|