pytal / deploy-env Goto Github PK

• Reference https://github.com/softprops/action-gh-release

• Minify bundle with terser
  • https://github.com/terser/terser#api-reference

Hi,

When adding a lot of env variables, I get rate limited by Vercel. However, it is currently not detected and eventually the command fails. Maybe detect & sleep for x seconds? Thanks!

Added Environment Variable NUXT_ENV_RECAPTCHA_KEY to Project umsfront [2s]
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
/bin/sh: -c: line 1: syntax error: unexpected end of file
/bin/sh: -c: line 0: `echo -n (xxxxx) | vercel env add NUXT_ENV_HOME_LEGAL production'
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 45 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 45 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 45 seconds (more than 120, code: "api-projects"). (429)
/bin/sh: more!: command not found
Vercel CLI 19.1.1
Error! Too many requests - try again in 44 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
/bin/sh: more!: command not found
Vercel CLI 19.1.1
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 39 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 38 seconds (more than 120, code: "api-projects"). (429)
/bin/sh: More!: command not found
Vercel CLI 19.1.1
Error! Too many requests - try again in 38 seconds (more than 120, code: "api-projects"). (429)
groups.: No such file or directory
Vercel CLI 19.1.1
Error! Too many requests - try again in 38 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 38 seconds (more than 120, code: "api-projects"). (429)

• Use new CLI syntax introduced in vercel CLI v22 https://github.com/vercel/vercel/releases/tag/vercel%4022.0.0

• Jest v27
  • Use esbuild in place of sucrase due to alangpierce/sucrase#638

Hi,

Thanks for your package.

Using node v12.18.2, I get this error;

w@Williams-MacBook-Pro umsFront % deploy-env
internal/modules/cjs/loader.js:969
throw err;
^

Error: Cannot find module 'fs/promises'
Require stack:

• /usr/local/lib/node_modules/deploy-env/lib/helpers/helpers.js
• /usr/local/lib/node_modules/deploy-env/lib/utils/vercel-env.js
• /usr/local/lib/node_modules/deploy-env/lib/cli.js
  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
  at Function.Module._load (internal/modules/cjs/loader.js:842:27)
  at Module.require (internal/modules/cjs/loader.js:1026:19)
  at require (internal/modules/cjs/helpers.js:72:18)
  at Object. (/usr/local/lib/node_modules/deploy-env/lib/helpers/helpers.js:1:135)
  at Module._compile (internal/modules/cjs/loader.js:1138:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
  at Module.load (internal/modules/cjs/loader.js:986:32)
  at Function.Module._load (internal/modules/cjs/loader.js:879:14)
  at Module.require (internal/modules/cjs/loader.js:1026:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
  '/usr/local/lib/node_modules/deploy-env/lib/helpers/helpers.js',
  '/usr/local/lib/node_modules/deploy-env/lib/utils/vercel-env.js',
  '/usr/local/lib/node_modules/deploy-env/lib/cli.js'
  ]
  }

I'm using a .env file, but if a env var have spaces, deploy-env trims them.

For example this env:
SOME_ENV=Some Important Env
Would translate to SomeImportantEnv when using deploy-env.

Is there a way to fix that? I've already tried using quotes, but it didn't work.

• Publish to npm
• Update GitHub release notes
• 🎉🎉🎉

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

• Support parsing .env.[deploymentEnv] files with dotenv
• Write documentation

• Publish to npm

• Limit concurrent exec promises
• Test

• Jest
  - Running scripts
  • Use sucrase for running scripts as esbuild doesn't have a drop-in node replacement

• Test CLI locally
• Test CLI installed from npm

Thanks a lot for this tool, I would like to use it with the latest vercel CLI. I am getting the following error:

Error! Environment Variable was not found.
Error! The Environment "API_URL" is invalid. It must be one of: <production | preview | development>.

Looking at the code, the issue come from a change in the vercel cli. Older CLI has:

 Vercel CLI 21.0.0
 vercel env [options] <command>
 add     [type] [name] [environment]     Add an Environment Variable (see examples below)

New CLI has:

Vercel CLI 23.0.1
vercel env [options] <command>
add     [name] [environment] [gitbranch]  Add an Environment Variable (see examples below)

which means [type]has been removed ([gitbranch]has been added).

Could you please update this project to the latest CLI version?

• Automate publish with GItHub Actions
• Test publish action

• Closed in 5593c2f

Released in v1.0.3

• Test .env file support
• Test v1.1.1

Is your feature request related to a problem? Please describe.
To be able to use this cli in Github actions or other CI solutions you need to pass the --token option with your vercel access token to the vercel cli

Describe the solution you'd like
Add a -t or --token option that is forwarded to the vercel cli

Describe alternatives you've considered

Additional context

• Refactor scripts
• Update package.json

• Update tsconfig
• Update required node version in package.json engines field

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update actions/setup-node action to v4
• Update dependency eslint to v9
• Update dependency eslint-config-prettier to v9
• Update dependency p-limit to v5
• Update dependency prettier to v3
• Update dependency vercel to v34
• Update pnpm to v9
• Update pnpm/action-setup action to v4
• Update softprops/action-gh-release action to v2
• Update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency esbuild to ^0.21.4
• Update dependency eslint to ^8.57.0
• Update dependency eslint-config-prettier to ^8.10.0
• Update dependency sucrase to ^3.35.0
• Update dependency terser to ^5.31.0
• Update typescript-eslint monorepo to ^5.62.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Update Node.js to v20 (node, @types/node)
• Update actions/checkout action to v4
• Update dependency typescript to v5
• Update jest monorepo to v29 (major) (@types/jest, jest)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

• Prettier
  • Configure
  • Format code
  • Format non-code files
  • Add workflow checks for CI
• ESLint
  • Configure
  • Fix lint errors
  • Add workflow checks for CI
• Integrate Prettier and ESLint

• Write documentation

Hi, I'm having the following error while executing deploy-env production:

(node:19829) UnhandledPromiseRejectionWarning: Error: Failed to find .rc file at default paths: [./.env-cmdrc,./.env-cmdrc.js,./.env-cmdrc.json]
at getRCFile (/home/guizz/.nvm/versions/node/v14.4.0/lib/node_modules/deploy-env/node_modules/env-cmd/dist/get-env-vars.js:108:11)
at async Object.exports.getEnvVarMap (/home/guizz/.nvm/versions/node/v14.4.0/lib/node_modules/deploy-env/lib/utils/get-env.js:1:386)
at async Object.exports.deployEnv (/home/guizz/.nvm/versions/node/v14.4.0/lib/node_modules/deploy-env/lib/utils/vercel-env.js:1:622)

Closed in dcabfc9

I use this tool on linux and it works great. I generate a .env.preview file then run deploy-env preview and it sets up all the vars correctly.

A co-worker uses mac, and whenever they run same command, they get a generated env file that looks correct, but after it's deployed, I get errors in the vercel log that point me to believing it's a bad env-var. I tried it on my own mac (with the same code) and it had a similar issue. it appears to be adding -n and \n to the var. I made an endpoint to dump the env-vars as json, and they look like this:

{
  "SOME_VAR": "-n MYVALUE\n"
}

when it should be:

{
  "SOME_VAR": "MYVALUE"
}

My .env.preview looks like this:

SOME_VAR=MYVALUE

Great package!

It would be great to add functionality to remove selected or all variables and to allow for multiple environments at once.

I.e. 

deploy-env delete or deploy-env delete [name of variable]
deploy-env --environment production preview development --var [name of variable]