next starter kit - ESM & Vite
#25
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
myovchev
commented
Nov 8, 2024
haroun
requested changes
Nov 11, 2024
myovchev
commented
Nov 11, 2024
| @@ -48,7 +47,8 @@ | |||
| "dependencies": { | |||
| "@apostrophecms/open-graph": "^1.2.1", | |||
| "@apostrophecms/seo": "^1.2.0", | |||
| "apostrophe": "^4.0.0", | |||
| "@apostrophecms/vite": "github:apostrophecms/vite", | |||
| "apostrophe": "github:apostrophecms/apostrophe", | |||
There was a problem hiding this comment.
FIXME: revert back to versions after release
Co-authored-by: haroun <[email protected]>
haroun
approved these changes
Nov 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The next branch is the official next release of the starter kit - ESM + Vite build.
What are the specific steps to test this change?
For example:
What kind of change does this PR introduce?
(Check at least one)
Make sure the PR fulfills these requirements:
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Other information: