Sean Massa
925c8ba18c
Publish Stable
...
- @vercel/build-utils@6.7.1
- vercel@28.18 .4
- @vercel/client@12.4.9
- @vercel/edge@0.3.2
- @vercel/error-utils@1.0.9
- @vercel/frameworks@1.3.4
- @vercel/fs-detectors@3.8.9
- @vercel/gatsby-plugin-vercel-analytics@1.0.9
- @vercel/gatsby-plugin-vercel-builder@1.2.7
- @vercel/go@2.4.4
- @vercel/hydrogen@0.0.62
- @vercel/next@3.7.4
- @vercel/node-bridge@4.0.1
- @vercel/node@2.10 .3
- @vercel/python@3.1.58
- @vercel/redwood@1.1.14
- @vercel/remix-entry-server@0.1.1
- @vercel/remix-builder@1.8.4
- @vercel/routing-utils@2.2.0
- @vercel/ruby@1.3.75
- @vercel/static-build@1.3.22
- @vercel/static-config@2.0.15
2023-04-07 16:43:42 -05:00
Espen Hovlandsdal
52b2892b80
[build-utils][cli][fs-detectors] Upgrade minimatch to 3.1.2 ( #9762 )
...
Minimatch 3.0.4 has a [ReDoS
vulnerability](https://security.snyk.io/vuln/SNYK-JS-MINIMATCH-3050818 ).
While not likely to be an issue for the packages that use it here, a
simple version bump should prevent the issue and reduce vulnerability
noise on audits. 3.1.2 is the latest version within the 3.x range, so
prevents breaking changes.
2023-04-06 16:18:07 -07:00
Nathan Rajlich
ee4ba6ccbe
[all] Use correct "license" field in package.json ( #9754 )
...
Follow-up to #9696 . Ensures that all packages in this repository have
the correct "license" field in their respective `package.json` files set
to "Apache-2.0", to match the `LICENSE` file at the root of the
repository.
The `LICENSE` file the authoritative source, so the "MIT" value was
incorrect. This change corrects the previous values and is not
considered a relicensing.
2023-04-06 15:33:55 -07:00
Nathan Rajlich
46348201b4
Publish Stable
...
- @vercel/build-utils@6.7.0
- vercel@28.18 .3
- @vercel/client@12.4.8
- @vercel/fs-detectors@3.8.8
- @vercel/gatsby-plugin-vercel-builder@1.2.6
- @vercel/go@2.4.3
- @vercel/hydrogen@0.0.61
- @vercel/next@3.7.3
- @vercel/node@2.10 .2
- @vercel/python@3.1.57
- @vercel/redwood@1.1.13
- @vercel/remix-builder@1.8.3
- @vercel/ruby@1.3.74
- @vercel/static-build@1.3.21
2023-03-29 12:25:26 -07:00
Nathan Rajlich
509926545e
[build-utils] Rename Lambda experimentalResponseStreaming prop to supportsResponseStreaming ( #9721 )
2023-03-29 12:11:09 -07:00
Sean Massa
54514a44af
Publish Stable
...
- @vercel/build-utils@6.6.0
- vercel@28.18 .2
- @vercel/client@12.4.7
- @vercel/fs-detectors@3.8.7
- @vercel/gatsby-plugin-vercel-builder@1.2.5
- @vercel/go@2.4.2
- @vercel/hydrogen@0.0.60
- @vercel/next@3.7.2
- @vercel/node-bridge@4.0.0
- @vercel/node@2.10 .1
- @vercel/python@3.1.56
- @vercel/redwood@1.1.12
- @vercel/remix-builder@1.8.2
- @vercel/ruby@1.3.73
- @vercel/static-build@1.3.20
2023-03-27 22:25:08 -05:00
Ethan Arrowood
0db8fadf74
[build-utils] add pnpm v8 auto detection ( #9720 )
...
Adds automatic detection for pnpm v8 based on lockfile v6
2023-03-27 23:07:39 +00:00
Steven
8391734b5e
[build-utils] Fix system env var detection for prefixed env vars ( #9709 )
...
This PR fixes a bug that was causing too many env vars to be exposed to the frontend by adding the framework `envPrefix`.
Some frameworks, such as CRA, will include all of these in the frontend even if not explicitly used so we must only prefix known [System Environment Variables](https://vercel.com/docs/concepts/projects/environment-variables/system-environment-variables ).
This PR adds an allowlist to ensure this is handle properly.
- Fixes https://linear.app/vercel/issue/VCCLI-639
2023-03-24 05:45:27 +00:00
Sean Massa
ab9915af32
Publish Stable
...
- @vercel/build-utils@6.5.0
- vercel@28.18 .0
- @vercel/client@12.4.6
- @vercel/fs-detectors@3.8.6
- @vercel/gatsby-plugin-vercel-builder@1.2.3
- @vercel/go@2.4.1
- @vercel/hydrogen@0.0.59
- @vercel/next@3.7.0
- @vercel/node@2.9.14
- @vercel/python@3.1.55
- @vercel/redwood@1.1.11
- @vercel/remix-builder@1.8.0
- @vercel/ruby@1.3.72
- @vercel/static-build@1.3.18
2023-03-22 12:37:51 -05:00
Chris Barber
d6dc27638c
[build-utils][next] Add prerender source path ( #9686 )
...
Adds the `sourcePath` for ISR prerender lambdas so that the front end can associate derived pages with the source route.
There's an accompanying `api` PR (https://github.com/vercel/api/pull/17940 ) which uses this deployment's tarballs to test the functionality. Here's the result:

Linear: https://linear.app/vercel/issue/VCCLI-410/communicate-how-functions-are-bundled
2023-03-22 17:16:44 +00:00
Nathan Rajlich
b2c68f1301
Publish Stable
...
- @vercel/build-utils@6.4.0
- vercel@28.17 .0
- @vercel/client@12.4.5
- @vercel/frameworks@1.3.3
- @vercel/fs-detectors@3.8.5
- @vercel/gatsby-plugin-vercel-builder@1.2.2
- @vercel/go@2.4.0
- @vercel/hydrogen@0.0.58
- @vercel/next@3.6.7
- @vercel/node@2.9.13
- @vercel/python@3.1.54
- @vercel/redwood@1.1.10
- @vercel/remix-builder@1.7.0
- @vercel/routing-utils@2.1.11
- @vercel/ruby@1.3.71
- @vercel/static-build@1.3.17
- @vercel/static-config@2.0.14
2023-03-16 12:23:51 -07:00
Sean Massa
ffdca76155
[gatsby-plugin-vercel-builder] link instead of move ( #9673 )
...
When creating the `./vercel/output/static` dir...
**Moving the `public` dir** is what currently happens. This causes Gatsby to believe that the build was not complete:
> info We've detected that the Gatsby cache is incomplete (the .cache directory exists but the public directory does not). As a precaution, we're deleting your site's cache to ensure there's no stale data.
**Copying the `public` dir** is not an option because it can cause a build to run out of space.
**Symlinking the `public` dir** would work, but it would require more changes throughout the system to make sure the symlink was followed properly.
**Hard Linking the `public` dir's files** is the best option. This PR links the directories instead of moving them. We did look for a library that already does the `hardlinkFileTree` thing, but couldn't find one.
---
**Testing**
This was manually tested with real deployments.
---
* paired with @TooTallNate
* [user report](https://github.com/vercel/vercel/issues/9452#issuecomment-1432858615 )
2023-03-16 18:00:56 +00:00
Steven
21a440b832
Publish Stable
...
- @vercel/build-utils@6.3.4
- vercel@28.16.15
- @vercel/client@12.4.4
- @vercel/fs-detectors@3.8.4
- @vercel/gatsby-plugin-vercel-builder@1.2.1
- @vercel/go@2.3.11
- @vercel/hydrogen@0.0.57
- @vercel/next@3.6.6
- @vercel/node@2.9.12
- @vercel/python@3.1.53
- @vercel/redwood@1.1.9
- @vercel/remix@1.6.2
- @vercel/ruby@1.3.70
- @vercel/static-build@1.3.16
2023-03-07 13:56:14 -05:00
Steven
48d925f105
Publish Stable
...
- @vercel/build-utils@6.3.3
- vercel@28.16.14
- @vercel/client@12.4.3
- @vercel/fs-detectors@3.8.3
- @vercel/gatsby-plugin-vercel-builder@1.2.0
- @vercel/go@2.3.10
- @vercel/hydrogen@0.0.56
- @vercel/next@3.6.5
- @vercel/node@2.9.11
- @vercel/python@3.1.52
- @vercel/redwood@1.1.8
- @vercel/remix@1.6.1
- @vercel/ruby@1.3.69
- @vercel/static-build@1.3.15
2023-03-07 13:17:14 -05:00
Sean Massa
cd09a38c19
[tests] skip recent flakey tests ( #9613 )
...
This test has been flakey on mac for a long time.
2023-03-07 17:21:53 +00:00
Sean Massa
e0f8bc9820
Publish Stable
...
- @vercel/build-utils@6.3.2
- vercel@28.16 .8
- @vercel/client@12.4.2
- @vercel/edge@0.3.1
- @vercel/frameworks@1.3.2
- @vercel/fs-detectors@3.8.2
- @vercel/gatsby-plugin-vercel-builder@1.1.10
- @vercel/go@2.3.9
- @vercel/hydrogen@0.0.55
- @vercel/next@3.6.2
- @vercel/node-bridge@3.1.13
- @vercel/node@2.9.9
- @vercel/python@3.1.51
- @vercel/redwood@1.1.7
- @vercel/remix@1.4.2
- @vercel/routing-utils@2.1.10
- @vercel/ruby@1.3.68
- @vercel/static-build@1.3.13
2023-02-28 10:26:29 -06:00
Steven
f0bc207717
[build-utils] Handle error during readConfigFile() ( #9542 )
...
This fixes a confusing error:
```
$ vercel build
Vercel CLI 28.16.6
Error: duplicated mapping key in "/vercel/path0/pnpm-lock.yaml" at line 1215, column -164:
/@react-dnd/asap/4.0.1:
^
```
2023-02-24 18:02:35 +00:00
Steven
34d199bd49
Publish Stable
...
- @vercel/build-utils@6.3.1
- vercel@28.16 .5
- @vercel/client@12.4.1
- @vercel/fs-detectors@3.8.1
- @vercel/gatsby-plugin-vercel-builder@1.1.8
- @vercel/go@2.3.8
- @vercel/hydrogen@0.0.54
- @vercel/next@3.6.0
- @vercel/node@2.9.7
- @vercel/python@3.1.50
- @vercel/redwood@1.1.6
- @vercel/remix@1.4.0
- @vercel/ruby@1.3.67
- @vercel/static-build@1.3.11
2023-02-22 20:23:55 -05:00
Steven
1dd421e1f6
[build-utils][next] Add images.contentDispositionType ( #9513 )
...
- Related to https://github.com/vercel/next.js/pull/46254
- Depends on https://github.com/vercel/api/pull/17434
2023-02-22 20:13:16 -05:00
Vincent Voyer
3d98d1cdea
Publish Stable
...
- @vercel/build-utils@6.3.0
- vercel@28.16 .0
- @vercel/client@12.4.0
- @vercel/fs-detectors@3.7.14
- @vercel/gatsby-plugin-vercel-builder@1.1.7
- @vercel/go@2.3.7
- @vercel/hydrogen@0.0.53
- @vercel/next@3.4.7
- @vercel/node@2.9.6
- @vercel/python@3.1.49
- @vercel/redwood@1.1.5
- @vercel/remix@1.3.3
- @vercel/ruby@1.3.65
- @vercel/static-build@1.3.9
- @vercel/static-config@2.0.13
2023-02-16 12:08:50 +01:00
Vincent Voyer
667af829c4
[build-utils][cli][client][node][next][static-config]: forward crons from vercel.json to config.json ( #9454 )
...
This PR changes the way cron jobs are being created in the build output
API. This is my first time contributing here. If you see something
unusual, let me know.
✅ Good for review
Our goal is to:
- Allow creating cron jobs via the `crons` property of `vercel.json` for
end users
- Allow framework authors to create cron jobs on Vercel via the `crons`
property of the Build Output API configuration
---
As you can see, we removed the previous implementation where cron jobs
could be configured at the function code level (export const cron = ""),
on top of vercel.json `functions` property. Here's why:
- All frameworks would have to implement the configure at the function
code level
- Not all frameworks can easily map a path to a specific function
(example: SvelteKit) and would have to bail on bundling functions inside
the same lambda
- Configuring a path + scheduler provides a better mapping of what cron
jobs are as of today: API routes on a schedule and not functions on a
schedule
- Dynamic routes Cron Jobs will be supported:
/api/crons/sync-slack-team/230
- Query parameters will be supported support:
/api/crons/sync-slack-team/230?secret=32k13l2k13lk21 (= securing cron
jobs v0)
- 100% frameworks compatibility from day one
Next.js and other frameworks may choose to implement their own cron jobs
feature that will then need to be configured through the `crons`
property of `config.json` (build output API).
cc @timneutkens @Rich-Harris
Internal thread:
https://vercel.slack.com/archives/C04DWF5HB6K/p1676366892714349
2023-02-16 11:49:09 +01:00
Sean Massa
9308a0fda5
Publish Stable
...
- @vercel/build-utils@6.2.4
- vercel@28.15 .6
- @vercel/client@12.3.10
- @vercel/frameworks@1.3.1
- @vercel/fs-detectors@3.7.13
- @vercel/gatsby-plugin-vercel-builder@1.1.6
- @vercel/go@2.3.6
- @vercel/hydrogen@0.0.52
- @vercel/next@3.4.5
- @vercel/node@2.9.5
- @vercel/python@3.1.48
- @vercel/redwood@1.1.4
- @vercel/remix@1.3.1
- @vercel/routing-utils@2.1.9
- @vercel/ruby@1.3.64
- @vercel/static-build@1.3.8
2023-02-15 12:26:53 -06:00
Luba Kravchenko
a606ab8678
[build-utils] add framework slug and version to build output ( #9448 )
...
Adds framework to Lambda and edge build outputs so that we can distinguish which framework they originated from when certain features should be applied to specific frameworks.
Breaking up https://github.com/vercel/vercel/pull/9447 into two parts:
This PR introduces the frameworks type. Part 2: https://github.com/vercel/vercel/pull/9449
ticket: ED-131
x-ref: [slack channel](https://vercel.slack.com/archives/C042LHPJ1NX )
2023-02-15 03:14:21 +00:00
Sean Massa
881e43a0e2
Publish Stable
...
- @vercel/build-utils@6.2.3
- vercel@28.15 .5
- @vercel/client@12.3.9
- @vercel/fs-detectors@3.7.12
- @vercel/gatsby-plugin-vercel-builder@1.1.5
- @vercel/go@2.3.5
- @vercel/hydrogen@0.0.51
- @vercel/next@3.4.4
- @vercel/node@2.9.4
- @vercel/python@3.1.47
- @vercel/redwood@1.1.3
- @vercel/remix-entry-server@0.1.0
- @vercel/remix@1.3.0
- @vercel/ruby@1.3.63
- @vercel/static-build@1.3.7
2023-02-14 15:38:34 -06:00
Felix Haus
200ac99647
[build-utils][cli] Remove 64 increment limit for serverless functions ( #9440 )
...
We no longer require the memory to be provided in steps of 64mb for
serverless functions.
Instead the memory can now be chosen freely from `128mb` to `3008mb` in
`1mb increments`.
Updates the `vercel.json` schema to reflect that change.
2023-02-14 13:08:40 -05:00
Felix Haus
1d3f2b5a62
[build-utils][cli] Update link to project-configuration ( #9439 )
...
The link to the documentation has changed.
It is now available under https://vercel.com/docs/concepts/projects/project-configuration
This updates:
- link generation `https://vercel.com/docs/configuration#project/ *` -> `https://vercel.com/docs/concepts/projects/project-configuration# *`
- Updates test files
- Updates static references of https://vercel.com/docs/configuration across the repo
2023-02-14 16:44:24 +00:00
Steven
8f49969585
[tests] Update tests script names ( #9433 )
...
### Description
These script names are currently really long and that makes it difficult
to read.
In particular, the most important part (the package name) is often
truncated.
See before/after below.
## Before
<img width="302" alt="image"
src="https://user-images.githubusercontent.com/229881/218588978-b8ed9a7a-f4da-4d58-af3f-2b1a7087737d.png ">
## After
<img width="290" alt="image"
src="https://user-images.githubusercontent.com/229881/218596895-65627ad0-2895-4bd7-8506-f5f545a419d3.png ">
2023-02-14 10:31:46 -05:00
Steven
b60d3f657a
[tests] Update CI to Node.js 16 ( #9397 )
...
In an effort to speed up CI, we should update the lowest common
denominator to Node.js 16
Note: In April, Node.js 14 will reach EOL so we can update tsconfig
targets and ship a major semver at that time.
---------
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2023-02-13 15:59:05 -05:00
Sean Massa
95a4dcfb33
Publish Stable
...
- @vercel/build-utils@6.2.2
- vercel@28.15 .4
- @vercel/client@12.3.8
- @vercel/fs-detectors@3.7.11
- @vercel/gatsby-plugin-vercel-builder@1.1.4
- @vercel/go@2.3.4
- @vercel/hydrogen@0.0.50
- @vercel/next@3.4.3
- @vercel/node-bridge@3.1.11
- @vercel/node@2.9.3
- @vercel/python@3.1.46
- @vercel/redwood@1.1.2
- @vercel/remix@1.2.13
- @vercel/ruby@1.3.62
- @vercel/static-build@1.3.6
2023-02-13 12:47:15 -06:00
Nathan Rajlich
a735527d8f
[build-utils] Filter out files outside of cwd when glob is in "follow" mode ( #9412 )
...
Enables `glob()` to operate in "follow" mode, but filters out any values where a symlink points to a target that lives outside of the `cwd.
2023-02-11 20:42:39 +00:00
JJ Kasper
c1c8b454cc
Publish Stable
...
- @vercel/build-utils@6.2.1
- vercel@28.15 .2
- @vercel/client@12.3.7
- @vercel/fs-detectors@3.7.10
- @vercel/gatsby-plugin-vercel-builder@1.1.2
- @vercel/go@2.3.3
- @vercel/hydrogen@0.0.49
- @vercel/next@3.4.1
- @vercel/node@2.9.2
- @vercel/python@3.1.45
- @vercel/redwood@1.1.1
- @vercel/remix@1.2.12
- @vercel/ruby@1.3.61
- @vercel/static-build@1.3.4
2023-02-07 11:51:17 -08:00
JJ Kasper
e2105e47b5
[build-utils] Add passQuery field to Prerender ( #9388 )
2023-02-06 16:57:17 -08:00
Andy Bitz
a585969dd3
Publish Stable
...
- @vercel/build-utils@6.2.0
- vercel@28.15 .1
- @vercel/client@12.3.6
- @vercel/fs-detectors@3.7.9
- @vercel/gatsby-plugin-vercel-builder@1.1.1
- @vercel/go@2.3.2
- @vercel/hydrogen@0.0.48
- @vercel/next@3.4.0
- @vercel/node@2.9.1
- @vercel/python@3.1.44
- @vercel/redwood@1.1.0
- @vercel/remix@1.2.11
- @vercel/ruby@1.3.60
- @vercel/static-build@1.3.3
2023-02-06 17:24:54 +01:00
Andy
d608153961
[next][build-utils] Add support for cron to vercel.json ( #9374 )
2023-02-06 12:28:41 +01:00
Andy Bitz
a4d16c681a
Publish Stable
...
- @vercel/build-utils@6.1.0
- vercel@28.15 .0
- @vercel/client@12.3.5
- @vercel/fs-detectors@3.7.8
- @vercel/gatsby-plugin-vercel-builder@1.1.0
- @vercel/go@2.3.1
- @vercel/hydrogen@0.0.47
- @vercel/next@3.3.21
- @vercel/node@2.9.0
- @vercel/python@3.1.43
- @vercel/redwood@1.0.54
- @vercel/remix@1.2.10
- @vercel/ruby@1.3.59
- @vercel/static-build@1.3.2
- @vercel/static-config@2.0.12
2023-02-01 23:26:52 +01:00
Andy
61bbd4f98b
[cli] Add crons to build output ( #9360 )
...
Co-authored-by: George Karagkiaouris <gkaragkiaouris2@gmail.com >
Co-authored-by: Chris Barber <chris.barber@vercel.com >
Co-authored-by: Nathan Rajlich <n@n8.io >
2023-02-01 22:47:55 +01:00
Steven
dbea973546
[build-utils][cli] Add env vars for VERCEL_PROJECT_SETTINGS_ ( #9332 )
...
This PR adds a few new environment variables for project settings.
This allows frameworks targeting the [Build Output API](https://vercel.com/docs/build-output-api/v3 ) to read data that is normally only available in through the `config` object when developing a [Builder/Runtime](https://github.com/vercel/vercel/blob/main/DEVELOPING_A_RUNTIME.md ).
This will also solve the problem of old Builders/Runtimes that never passed the `config` through to `getNodeVersion()`.
- Related to https://github.com/unjs/nitro/pull/879
2023-01-31 23:27:36 +00:00
chloetedder
ada9a48d57
Publish Stable
...
- @vercel/build-utils@6.0.1
- vercel@28.14 .1
- @vercel/client@12.3.4
- @vercel/fs-detectors@3.7.7
- @vercel/gatsby-plugin-vercel-builder@1.0.3
- @vercel/go@2.3.0
- @vercel/hydrogen@0.0.46
- @vercel/next@3.3.20
- @vercel/node@2.8.17
- @vercel/python@3.1.42
- @vercel/redwood@1.0.53
- @vercel/remix@1.2.9
- @vercel/ruby@1.3.58
- @vercel/static-build@1.3.1
2023-01-30 15:19:54 -07:00
Chris Barber
89a15681d5
[build-utils] Rewrite rename() to be more efficient ( #9322 )
...
Around 6 months ago, @styfle brought to my attention how `rename()` in build-utils used `reduce()` and could be written better. So, I rewrote it.
Before, the code would create a new `Files` object and copy the contents of the previous `Files` object. This caused heavy garbage collection and memory thrashing.
Instead, I created a single `Files` object, then add the files to it.
Results:
| # Files | Before | After |
|---|---|---|
| 1,000 | 75 ms | 1 ms |
| 10,000 | 10.6 s | 7 ms |
| 20,000 | 44.6 s | 16 ms |
| 30,000 | 105.5 s | 22 ms |
| 100,000 | Too long | 73 ms |
2023-01-27 18:21:59 +00:00
Steven
25f6595d36
Publish Stable
...
- @vercel/build-utils@6.0.0
- vercel@28.13 .2
- @vercel/client@12.3.3
- @vercel/edge@0.2.7
- @vercel/frameworks@1.3.0
- @vercel/fs-detectors@3.7.6
- @vercel/gatsby-plugin-vercel-builder@1.0.1
- @vercel/go@2.2.31
- @vercel/hydrogen@0.0.45
- @vercel/next@3.3.19
- @vercel/node@2.8.16
- @vercel/python@3.1.41
- @vercel/redwood@1.0.52
- @vercel/remix@1.2.8
- @vercel/ruby@1.3.57
- @vercel/static-build@1.2.1
2023-01-26 11:19:03 -05:00
Steven
2004e3d734
[tests] Fix jest-haste-map: Haste module naming collision ( #9317 )
...
```
jest-haste-map: Haste module naming collision: app-three
The following files share their name; please adjust your hasteImpl:
* <rootDir>/test/fixtures/33-hybrid-monorepo/backend/app-three/package.json
* <rootDir>/test/fixtures/34-monorepo-no-workspaces/backend/app-three/package.json
```
2023-01-26 00:59:39 +00:00
Chris Barber
1a4f185045
[build-utils] Removed unused execAsync() function ( #9200 )
...
This function can sometimes give a TypeScript error if @types/node says 'code' should be a `number | null` and yet the code is returns as a `number`:
```
@vercel/build-utils:build: src/fs/run-user-scripts.ts(140,13): error TS2322: Type 'number \| null' is not assignable to type 'number'.
@vercel/build-utils:build: Type 'null' is not assignable to type 'number'.
```
I'm not sure if there are any other projects that depend on `@vercel/build-utils`, but it doesn't appear that the Vercel CLI nor the build container use this `execAsync()` function. If I'm mistaken, feel free to close this PR.
As this removal is a breaking change, setting the semver to major and not auto-merging unless others are in agreement.
2023-01-24 01:05:44 +00:00
Steven
4ccdcde463
Publish Stable
...
- @vercel/build-utils@5.9.0
- vercel@28.12 .6
- @vercel/client@12.3.1
- @vercel/fs-detectors@3.7.5
- @vercel/go@2.2.30
- @vercel/hydrogen@0.0.44
- @vercel/next@3.3.15
- @vercel/node@2.8.13
- @vercel/python@3.1.40
- @vercel/redwood@1.0.51
- @vercel/remix@1.2.5
- @vercel/ruby@1.3.56
- @vercel/static-build@1.1.7
2023-01-17 19:25:26 -05:00
Nathan Rajlich
22d3ee160b
[build-utils] Add includeDirectories option to glob() ( #9245 )
...
Instead of always including empty directories in `glob()`, make it an
opt-in behavior because technically it's a breaking change to include
them by default.
2023-01-17 19:21:40 -05:00
Sean Massa
b5cdc82a1c
Publish Stable
...
- @vercel/build-utils@5.8.3
- vercel@28.12 .4
- @vercel/client@12.2.31
- @vercel/edge@0.2.6
- @vercel/error-utils@1.0.8
- @vercel/frameworks@1.2.4
- @vercel/fs-detectors@3.7.4
- @vercel/gatsby-plugin-vercel-analytics@1.0.6
- @vercel/go@2.2.29
- @vercel/hydrogen@0.0.43
- @vercel/next@3.3.14
- @vercel/node-bridge@3.1.8
- @vercel/node@2.8.11
- @vercel/python@3.1.39
- @vercel/redwood@1.0.50
- @vercel/remix@1.2.4
- @vercel/routing-utils@2.1.8
- @vercel/ruby@1.3.55
- @vercel/static-build@1.1.6
- @vercel/static-config@2.0.11
2023-01-13 15:45:03 -06:00
Sean Massa
e54da8a2e5
Publish Stable
...
- @vercel/build-utils@5.8.2
- vercel@28.12 .3
- @vercel/client@12.2.30
- @vercel/edge@0.2.5
- @vercel/error-utils@1.0.7
- @vercel/frameworks@1.2.3
- @vercel/fs-detectors@3.7.3
- @vercel/gatsby-plugin-vercel-analytics@1.0.5
- @vercel/go@2.2.28
- @vercel/hydrogen@0.0.42
- @vercel/next@3.3.13
- @vercel/node-bridge@3.1.7
- @vercel/node@2.8.10
- @vercel/python@3.1.38
- @vercel/redwood@1.0.49
- @vercel/remix@1.2.3
- @vercel/routing-utils@2.1.7
- @vercel/ruby@1.3.54
- @vercel/static-build@1.1.5
- @vercel/static-config@2.0.10
2023-01-13 15:06:45 -06:00
Sean Massa
b793a67588
Publish Stable
...
- @vercel/build-utils@5.8.1
- vercel@28.12 .2
- @vercel/client@12.2.29
- @vercel/edge@0.2.4
- @vercel/error-utils@1.0.6
- @vercel/frameworks@1.2.2
- @vercel/fs-detectors@3.7.2
- @vercel/gatsby-plugin-vercel-analytics@1.0.4
- @vercel/go@2.2.27
- @vercel/hydrogen@0.0.41
- @vercel/next@3.3.12
- @vercel/node-bridge@3.1.6
- @vercel/node@2.8.9
- @vercel/python@3.1.37
- @vercel/redwood@1.0.48
- @vercel/remix@1.2.2
- @vercel/routing-utils@2.1.6
- @vercel/ruby@1.3.53
- @vercel/static-build@1.1.4
- @vercel/static-config@2.0.9
2023-01-13 15:01:55 -06:00
Sean Massa
e71d5638ee
Publish Stable
...
- @vercel/build-utils@5.8.0
- vercel@28.12 .1
- @vercel/client@12.2.28
- @vercel/edge@0.2.3
- @vercel/error-utils@1.0.5
- @vercel/frameworks@1.2.1
- @vercel/fs-detectors@3.7.1
- @vercel/gatsby-plugin-vercel-analytics@1.0.3
- @vercel/go@2.2.26
- @vercel/hydrogen@0.0.40
- @vercel/next@3.3.11
- @vercel/node-bridge@3.1.5
- @vercel/node@2.8.8
- @vercel/python@3.1.36
- @vercel/redwood@1.0.47
- @vercel/remix@1.2.1
- @vercel/routing-utils@2.1.5
- @vercel/ruby@1.3.52
- @vercel/static-build@1.1.3
- @vercel/static-config@2.0.8
2023-01-13 14:47:25 -06:00
Ethan Arrowood
a008c9c7fe
[build-utils] Support empty directory entries for glob() and download() ( #9164 )
...
Reopening #9103 since it was reverted.
2023-01-13 12:01:37 -08:00
Sean Massa
62b28ad0b4
Publish Stable
...
- @vercel/build-utils@5.7.6
- vercel@28.12 .0
- @vercel/client@12.2.27
- @vercel/edge@0.2.2
- @vercel/error-utils@1.0.4
- @vercel/frameworks@1.2.0
- @vercel/fs-detectors@3.7.0
- @vercel/gatsby-plugin-vercel-analytics@1.0.2
- @vercel/go@2.2.25
- @vercel/hydrogen@0.0.39
- @vercel/next@3.3.10
- @vercel/node-bridge@3.1.4
- @vercel/node@2.8.7
- @vercel/python@3.1.35
- @vercel/redwood@1.0.46
- @vercel/remix@1.2.0
- @vercel/routing-utils@2.1.4
- @vercel/ruby@1.3.51
- @vercel/static-build@1.1.2
- @vercel/static-config@2.0.7
2023-01-13 14:00:46 -06:00