-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not support includeFiles and excludeFiles glob patterns, which Vercel requires #104
Comments
Hi, thanks for great report. I have tested current version (0.3.1) and it works.
Take a look at my examples (https://github.com/juicyfx/vercel-php/tree/master/test/examples/18-exclude-files) |
Aha! That likely explains my issues: I was using a Will see if I can construct an |
Yep, that's catchy. :-) Vercel is using glob and it's using minimatch. You can test it here https://globster.xyz/. |
I am closing it now, feel free open it again. |
Bug report
0.3.1
Description
Vercel requires a function's
includeFiles
andexcludeFiles
to be a single glob string.vercel-php
expects an array, or a string. But it trips on many glob matching patterns.There are two abutting issues:
now.json
vercel.json
file with an array inincludeFiles
orexcludeFiles
fails validation and refuses to deploy, even though that's what's recommended invercel-php
's documentation.vercel-php
seems to trip on many non-trivial glob patterns (basically anything that's beyond a string ending in*
or**
). It will deploy, but with the following behavior:On the first GET request, the request times out with a Vercel 502
NO_RESPONSE_FROM_FUNCTION
error.Vercel logs show the following:
On all subsequent requests, PHP returns
PHP Built-In Server HTTP error: Error: connect ECONNREFUSED 127.0.0.1:8000
.Vercel logs show:
My temporary workaround is to use a single string with a simple glob pattern that
vercel-php
does seem to do okay with; in my case:excludeFiles: projects/**
.Glob patterns I've encountered this issue with:
!(file)
(fileA|fileB)
(doesn't error, but appears to get parsed as a single exact filename, rather than a glob pattern)**/*
The text was updated successfully, but these errors were encountered: