Comments (4)
One thing that was strange to me when using Sapper is that in order to get typings for these library functions, I had to build Sapper once so the corresponding files and its definitions are generated and typescript can pick them up. I'd like to find a solution where, from an editor/TS perspective, this would not be needed anymore, because as soon as you really build this project, the files are there.
from kit.
I think that should be possible, as long as aliases are correctly set up in tsconfig.json
— since Snowpack supports TS out of the box, we can just make sure that those modules are written in TS and everything should Just Work (he said confidently)
from kit.
I just merged #68 which handles types for imports from @sveltejs/kit/client
, but as explained there I'm not sure that's what we want
from kit.
Closing in favour of #82, which is related
from kit.
Related Issues (20)
- +page.svelte switching erratically HOT 3
- `preloadData` should be able to cache multiple routes at a time
- Sveltekit server components HOT 2
- Enable adapter-static to connect with adapter-node backend by simply supplying URL HOT 2
- immutable chunks output is different every build for chunks depending on `$app/stores` HOT 1
- Multiple rest parameters: Make eagerness configurable or respect parameter matcher HOT 2
- Add a `%svelte.version%` template placeholder to propagate the current `kit.version.name` to app.html HOT 2
- Trailing slash on homepage HOT 1
- Add CSS @layer support for components, tailwind v4
- Email validator on $page.form is outdated or just wrong HOT 3
- Allow a task to be formed when the application is initialized. HOT 6
- Redirects in "PageServerLoad" does result in 500 internal error within in a pnpm workspace if "preserveSymlinks" is used in vite.config.ts
- Volatile paths in generated `tsconfig.json` in monorepo
- sveltekit removes all styles from head HOT 3
- Shallow routing doesn't work correctly
- Error parsing +svelte.page when the script section contains "</script>" in comment or in string HOT 1
- My SvelteKit Application that uses Prisma JS throws this error in Production: `TypeError: Failed to resolve module specifier ".prisma/client/index-browser". Relative references must start with either "/", "./", or "../".` which is hosted on Vercel. HOT 2
- hooks transformPageChunk html not replacing class HOT 1
- export csr = '/custom.js' HOT 2
- Disabling SSR does not work HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kit.