feat: handle multilines in env files

[antongolub]

continues #974

const multiline = `SIMPLE=xyz123
NON_INTERPOLATED='raw text without variable interpolation'
MULTILINE = """
long text here,
e.g. a private SSH key
"""
ENV=v1\nENV2=v2\n\n\n  ENV3  =    v3   \n   export ENV4=v4
`

assert.deepEqual(parseDotenv(multiline), {
  SIMPLE: 'xyz123',
  NON_INTERPOLATED: 'raw text without variable interpolation',
  MULTILINE: '\nlong text here,\ne.g. a private SSH key\n',
  ENV: 'v1',
  ENV2: 'v2',
  ENV3: 'v3',
  ENV4: 'v4',
})

fyi, @1e9y , @easymikey

• Tests pass
• Appropriate changes to README are included in PR

[1e9y]

Why not use more readable variable names?

[antongolub]

Just a minification challenge without any special reason.

(s)pace(r)egex
(k)ey(r)egex

(e)nv
(k)ey
(b)uffer
(q)oute
(i)gnore
(c)har

[1e9y]

Lets make it contributor-friendly and leave minification for Vite plugin!

[antongolub]

dotenv requires ~10Kb extra

cjs without treeshaking
https://github.com/motdotla/dotenv/blob/3ca0fd0c3005b5f92d69b6ff4661e722394c1ab7/lib/main.js#L12

[antonmedv]

I’m against adding support for this feature.

[antongolub]

I'm afraid, it's dotenv format requirement:

• https://github.com/motdotla/dotenv/blob/master/tests/.env-multiline
• https://hexdocs.pm/dotenvy/dotenv-file-format.html

[easymikey]

Cool, нou've put it in a separate package :)