language-tools
next-runtime
language-tools | next-runtime | |
---|---|---|
23 | 12 | |
1,168 | 600 | |
1.9% | 1.2% | |
8.9 | 9.2 | |
7 days ago | 6 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
language-tools
- code whisperer not working with svelte project
-
How to configure the svelte language server with nvim?
I don't use nvchad, I use vanilla neovim with mason + lspconfig, but in the issues section there is a hint https://github.com/sveltejs/language-tools/issues/2008
- A love story of Svelte and JSX ๐
-
Svelte formatter stopped working
I've opened an issue on the sveltejs repo on GitHub (there's more info there, like steps to reproduce) and haven't got any answers yet, so I'm hoping I'll have better luck here, maybe someone has faced this before.
-
VS Code Svelte extension: Can the `css-unused-selector` warning be ignored per instance?
It was a bit hard to understand but after reading this issue, it worked for me like this:
-
Does Svelte's LSP "extract into const/function/component refactorings" code actions work for you?
Hi. I just got into Svelte today and I was wondering about the Svelte LSP's features. I found this issue https://github.com/sveltejs/language-tools/issues/83, which indicates that "extract into const/function/component refactorings" code actions are already implemented for the Svelte LSP.
- Svelte will gain first-class support in JetBrains WebStorm 2022.3
-
State of JSX in JavaScript Frameworks
However, the Svelte Language Tools does leverage JSX for type checking via svelte2tsx.
-
Svelte quick tip: style prop defaults
Not yet, but thereโs an open issue: https://github.com/sveltejs/language-tools/issues/1326
-
Add lint-staged To SvelteKit Project
svelte-check: check only files mentioned as arguments #353
next-runtime
-
5 Ways to Redirect URLs in Next.JS
I say "when it works" because it's not necessarily supported by all hosts. For example, Vercel of course supports it, but Netlify doesn't currently appear to. As for other hosts, you'd need to verify with them, but I'd imagine it varies.
-
My 2023 Year in Review
View on GitHub
-
4./ Client components in static and dynamic routes before Next 13
Note: at the time of writing this, there is a bug in Next (13.4.7). Although Next guarantees that you can use both app router and pages router in the same project, there is a bug that causes a full page reload when you browse from an app route to a pages route or vice versa. This is unfortunate but does not influence our tests.
-
My experience deploying a Next.js application on Netlify (using Next App Router)
So adding an edge function was the only workaround I found. Apparently it's an issue they're working on and I think it should be set as high priority since trailing slashes matter for SEO.
- What is server costs (resources) with Next.js ISR?
-
Next.js rewrites
Here are a great guide on what to use when: https://github.com/netlify/netlify-plugin-nextjs/blob/main/docs/redirects-rewrites.md
-
Netlify: Improved workflow and new role for pricing changes
It also seems like an unconscious acknowledgement that their add-on services (form handling, post-processing, identity, analytics, auth, etc.) are woefully inadequate in some cases and uncompetitive in others. $20/mo for form handling beyond 100 submissions? Okay, maybe. But the feature set is so bare it's laughable. There's minimal to no customization for notification emails, no confirmation emails, and their post-processing for form detection will bring the speed of your build pipeline to its knees on any serious site. On one site turning off post-processing yielded a build time reduction of more than double the actual build time of the site.
Not to mention the fact that by foregoing any concept of a server and forcing everything into some flavor of lambda they've created a scenario where every framework with any such functionality requires open source shepherding to function on their platform[0]. At best they've diluted their initial mission and at worst they've created an unmanageable mess. They can't even make Next.js work on their platform without causing what should issue 404s to return 500s instead[1]. The SEO implications for that are a potential death sentence and that issue has now been open for five months.
I was very optimistic about Netlify at the outset, and it worked great and still continues to work great for our test cases where we've deployed individual LPs. Where the pain seems to start is anything above a thousand pages or more, which is also coincidentally where the stakes start to get higher. I don't know how they could expect anyone at an enterprise or growing business to seriously scrutinize this platform and view it as ideal with that in mind.
[0]: https://github.com/netlify/netlify-plugin-nextjs
-
Next.js measurement: Serve images in next-gen formats even when using next/image
I don't think Netlify supports WebP currently: https://github.com/netlify/netlify-plugin-nextjs/issues/687
- Vercel Welcomes Rich Harris, Creator of Svelte
-
Make a Custom Portfolio Site Generator with StepZen's Developer Publishing Pack
I made the template here using NextJS, because Netlify has a NextJS plugin, which automates the process of using serverless functions. I inserted the call to my StepZen GraphQL endpoint in the pages/api folder to keep sensitive info off the client.
What are some alternatives?
nvim-lspconfig - Quickstart configs for Nvim LSP
joystick - A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
prepack - A JavaScript bundle optimizer.
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
services - Real World Micro Services
sveltekit-tooling - SvelteKit tooling: we look at 7 tools you can add to streamline your Svelte continuous integration (CI) and development processes.
denoflare - Develop, test, and deploy Cloudflare Workers with Deno.
react-use - React Hooks โ ๐
SvelteKit - web development, streamlined
ember-render-modifiers - Implements did-insert / did-update / will-destroy modifiers for emberjs/rfcs#415