[Discussion] template-svelte-ts

Just ongoing discussion about new TS features of TRL and template-svelte-ts.

11 Replies

Vauxs•5mo ago

It gets rid of the issue, yes. Also I only now realized the template repo has eslint configs The problem is that eslintrc is no longer a thing, replaced with eslint.config.js

TyphonJS (Michael)OP•5mo ago

It's a tricky thing in this case as the rule is there to prevent an antiquated way of code organization, but by default doesn't like the use case that is valid. IE no code is going in the namespace just types. It's rather convenient with the import / export semantics because you just need to...

import { Thing } from './thing';

new Thing(options: Thing.Options);

import { Thing } from './thing';

new Thing(options: Thing.Options);

Instead of having many separate symbols / separate imports. The default Svelte 4 declaration generation produces 4 symbols per component. The component and separate type aliases for Props, Events, & Slots. It doesn't uniquely name the type aliases. It also doesn't help library authors who want to export these type aliases. IE you have to do:

export { default as MyComponent } from './MyComponent.svelte';
export * from './MyComponent.svelte';

export { default as MyComponent } from './MyComponent.svelte';
export * from './MyComponent.svelte';

I solved that problem as well in my Svelte declaration support by converting the output of the Svelte declaration generation and modifying things to use namespaces for types. When you do:

export { default as MyComponent } from './MyComponent.svelte';

export { default as MyComponent } from './MyComponent.svelte';

You get complete access to all of the types. MyComponent.Props, etc. Some of the machinations the Svelte maintainers came up with like - ComponentEvents - ComponentProps are entirely unnecessary.. Yes.. I need to update my TJS configs and the eslint setup as mentioned. template-svelte-ts was an old repo with old setup. This is a situation of having lots of other fish to fry that are more important even though this is a nagging issue for end developers. ESlint in general is opinionated and should be setup per project / user preferences. A good deal of devs probably won't like my opinions like the code formatting that I use / allman style, etc. Lots of devs are also lazy, so having a good set of defaults is nice. Most might not even run the eslint command.

Vauxs•5mo ago

Every single time I look at how your imports are structured...

TyphonJS (Michael)OP•5mo ago

Like a sane person!!! ;P

Vauxs•5mo ago

You waste so much space!!!! And no sane person has brackets have a newline at the beginning but not have one at the end

import {
          Thing,
          OtherThing }           from 'module'

import {
          Thing,
          OtherThing }           from 'module'

is not sane :wokeJoy:

Vauxs•5mo ago

Anyway by the looks of it, yes, there are no alternatives to namespaces beyond what you mentioned is unnecessary https://www.reddit.com/r/typescript/comments/1d3zpow/alternative_to_using_namespaces/

From the typescript community on Reddit

Explore this post and more from the typescript community

TyphonJS (Michael)OP•5mo ago

In your own projects you are free to choose the code organization / styling that you prefer.

Vauxs•5mo ago

Obviously

TyphonJS (Michael)OP•5mo ago

But yeah.. Having a proper eslint setup w/ TS & Svelte support though it will eventually use my config updates is a starting point for devs... Changing the config to something that one prefers is then recommended. Just did some sprucing up of the template repo. I did decide on removing the bespoke Rollup plugin. I'm a big fan of KISS especially for a template repo. README instructions mention running npm run build to create initial dist/ assets.

Vauxs•5mo ago

Its been a common issue whenever I had others fork my modules :/ So much so one literally submitted that plugin But fine. Also if we are going KISS, I'd argue the postcss and terser plugins also should go All it does is obfuscate

TyphonJS (Michael)OP•5mo ago

Well.. I am eventually going to create a CLI for building / no need for a Vite config at some point. Also a thorough dev guide and onboarding materials. Alas I've spent too much time in the bowels of lower level dev and haven't spent as much time near the surface / new dev experience, etc. Can't help if folks don't read the README. 😉 I did put a notice on not "skipping step 9"....

Gaming

Programming

[Discussion] template-svelte-ts

Did you find this page helpful?