Skip to content

Conversation

@yusinto
Copy link
Contributor

@yusinto yusinto commented Mar 8, 2024

Fixes #379 . I have tested this locally and verified the type errors are fixed and the example application (complete) still works.

Comment on lines +16 to +17
"packages/sdk/vercel/examples/complete",
"packages/sdk/vercel/examples/route-handler",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Include examples in the workspace to take advantage of the monorepo setup.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No functional changes here just minor refactoring for the sake of my ocd.

Comment on lines +13 to +14
"@launchdarkly/vercel-server-sdk": "1.3.0",
"@vercel/edge-config": "^1.1.0",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are the main updates.

@shortcut-integration
Copy link

This pull request has been linked to Shortcut Story #235330: Major update for vercel edge config.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

appDir is now part of @vercel/edge-config and no longer experimental. Hence this file is unnecessary.

Comment on lines +12 to +14
"@launchdarkly/vercel-server-sdk": "1.3.0",
"@vercel/edge-config": "^1.1.0",
"next": "14.1.2",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Major updates here too.

"test": "NODE_OPTIONS=\"--experimental-vm-modules --no-warnings\" jest --ci --runInBand",
"coverage": "yarn test --coverage",
"check": "yarn prettier && yarn lint && yarn build && yarn test && yarn doc"
"check": "yarn prettier && yarn lint && yarn build && yarn test"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doc never exists in this project, so this was breaking.

token: '',
version: '',
type: 'vercel',
},
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is newly added in the major version of edge-config.

!process.env.LD_CLIENT_SIDE_ID ||
!parseConnectionString(process.env.EDGE_CONFIG)
) {
return NextResponse.rewrite(new URL('/missing-edge-config', request.url));
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure how this example could have worked? request does not exist.

false,
);

return hotDogFaviconEnabled
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same applies to request here as above.

@yusinto yusinto requested a review from ldhenry March 8, 2024 01:09
@kinyoklion
Copy link
Member

If you want to release this, versus bundling it with other changes in the future, then don't use chore. If we want a releasable unit that isn't fix, fix!, feat, or feat!, then we could configure one. But it is probably easiest to choose one of those.

@yusinto yusinto changed the title chore: Update to major version of @vercel/edge-config feat: Update to major version of @vercel/edge-config Mar 8, 2024
@yusinto
Copy link
Contributor Author

yusinto commented Mar 8, 2024

This should be a feat, because it breaks the previous version types.

@kinyoklion
Copy link
Member

This should be a feat, because it breaks the previous version types.

A customer will need to update their code with this upgrade? If so feat!: The exclamation point indicates breaking changes.

@yusinto yusinto changed the title feat: Update to major version of @vercel/edge-config fix: Update to major version of @vercel/edge-config Mar 8, 2024
@yusinto
Copy link
Contributor Author

yusinto commented Mar 8, 2024

@kinyoklion I changed this to fix because I tested this PR and it does not break existing usage. If anything, it fixes the EdgeConfigClient type mismatch in init as described in #379 .

@yusinto yusinto enabled auto-merge (squash) March 8, 2024 21:49
@kinyoklion
Copy link
Member

I know it isn't related to this PR, but is detox e2e unstable? Because of how our releases work we need to be extra careful that CI jobs are stable.

@yusinto
Copy link
Contributor Author

yusinto commented Mar 11, 2024

is detox e2e unstable

It used to be stable but it has declined to be not stable. It's very disappointing but I may have to disable/exclude it completely, or else only run it when RN changes are made. I'll create a separate PR to fix this.

@yusinto
Copy link
Contributor Author

yusinto commented Mar 14, 2024

The detox tests are definitely flaky in CI although they are stable locally when run through act. It's disappointing. It's successful here now, but I'll make it non-mandatory/remove it in a separate PR.

@yusinto yusinto merged commit bbaf01c into main Mar 14, 2024
@yusinto yusinto deleted the yus/sc-235330/major-update-for-vercel-edge-config branch March 14, 2024 21:54
@github-actions github-actions bot mentioned this pull request Mar 14, 2024
yusinto pushed a commit that referenced this pull request Mar 14, 2024
🤖 I have created a release *beep* *boop*
---


<details><summary>vercel-server-sdk: 1.3.1</summary>

##
[1.3.1](vercel-server-sdk-v1.3.0...vercel-server-sdk-v1.3.1)
(2024-03-14)


### Bug Fixes

* Update to major version of @vercel/edge-config
([#393](#393))
([bbaf01c](bbaf01c))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
yusinto added a commit that referenced this pull request Mar 19, 2024
We updated @vercel/edge-config package to use the major version in this
[pr](#393) however I
overlooked updating the corresponding example apps to use the workspace
versions of our vercel sdk.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update @vercel/edge-config dependency

3 participants