-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
fix: backwards compatibility for types #8721
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
📝 Ran ecosystem CI: Open
|
fs.mkdirSync('types/faux', { recursive: true }); | ||
fs.readdirSync('src/runtime', { withFileTypes: true }) | ||
.filter((dirent) => dirent.isDirectory()) | ||
.forEach((dirent) => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this include internal? Should be filtered out probably
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
📝 Ran ecosystem CI: Open
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
I think most things are fixed, one is missing: |
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
Ok I found a workaround for the dts-buddy bug. Ecosystem CI run looks mostly good now. SvelteKit tests - no idea why they failed, maybe unrelated. language-tools: one needs a change in language-tools due to where the |
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
Nice, ecosystem-ci is green again (that red cross from language tools is a timeout, that happens from time to time) |
HEADS UP: BIG RESTRUCTURING UNDERWAY
The Svelte repo is currently in the process of heavy restructuring for Svelte 4. After that, work on Svelte 5 will likely change a lot on the compiler aswell. For that reason, please don't open PRs that are large in scope, touch more than a couple of files etc. In other words, bug fixes are fine, but feature PRs will likely not be merged.
Before submitting the PR, please make sure you do the following
feat:
,fix:
,chore:
, ordocs:
.Tests
npm test
and lint the project withnpm run lint