What about additional loaders: + Pug, TypeScript, SASS, material-vue ?

[ac2epsilon]

Is your feature request related to a problem? Please describe.
It may be good add some productivity tools to tool chain

Describe the solution you'd like
What about additional loaders: + Pug, TypeScript, SASS, material-vue ? All of these are proven good with both, Vue and Nuxt. I see no point to make branch on this. It is question of one npm -D.

Describe alternatives you've considered
Anything here is not a question at all, excepting vue-material support is newer than vuetify's, and later is more nuxt-ish and have longer nuxt track/ this can be point of discussion but both are stable and no very difference which will be accepted. All of this save on typing with no addition obligations.

Not if no. Let if yes

[liyasthomas]

All our components are custom elemnts we built from time to time on request. This kept us to keep the dependency list to the minimum. But seriously, PW do lack a UI library. Vuetify seems like a solid option for that.

Pug, TypeScript, SASS

It's amazing what bare Vue/Nuxt app can do with only SCSS and JS (HTML + CSS + JS). A transpiled TS branch or any other language is good. But nobody requested it so far. I'll wait for a discussion on that.

[AndrewBastin]

@liyasthomas Actually I have been thinking of requesting a gradual migration to TypeScript as well, having the static types are really helpful to prevent the tiny mistakes we make while coding stuff up and also with the growing complexity of the app, it makes much more sense to have typings.

[liyasthomas]

I'll add a new branch for Typescript

[liyasthomas]

Tada! TypeScript branch: https://github.com/liyasthomas/postwoman/tree/typescript

Initial configs are incomplete and will produce runtime errors.

Nuxt Offical Guide: https://typescript.nuxtjs.org/

[Sn005]

@liyasthomas
Hi!
I Want to support resolve runtime errors by TypeScript.
If so, what should I do?
Can I create a new branch and send a pull request to the typescript branch?

I look forward to your reply.

[liyasthomas]

Actually, configs have been resolved to start a MVP. Now the remaining process is to compile each methods to typed functions / classes, which is a long task.

You can start contributing by:

1. Git clone https://github.com/liyasthomas/postwoman/tree/typescript
2. Install dependencies: npm i
3. Start local dev server: npm run dev
4. Convert all *.js to typed *.ts files
5. Convert all *.vue files to typed functions / classes

Official guide: https://typescript.nuxtjs.org/

Don't forget to mention <script lang="ts"> for TypeScript scripts inside *.vue files.

[Sn005]

@liyasthomas

Thank you for your reply.
OK.
I understand how to contribute.
It's a long task, but I'm working on it.

[liyasthomas]

We've Telegram group: https://t.me/postwoman_app
And Discord server: https://discord.gg/GAMWxmR
for communication outside GitHub.

[AndrewBastin]

@Sn005 if you don't mind, I might also be working on this, I kinda know the typescript toolchain inside out as I usually work on TypeScript (gotta love dem type checks) and I would love to get this done ASAP.

[AndrewBastin]

And also since this issue thread mostly focuses on TypeScript support, I would like this issue renamed.

[Sn005]

@AndrewBastin
No problem.
I am grateful because my usual work is busy.
However, I'm curious about how to proceed with long tasks.
I also want to commit to this task.
So, It would be helpful if you could share how to proceed with the task each time.

[AndrewBastin]

@Sn005 sure, well, right now my PR is up on this repo, we could certainly use your help with making the typings more strong as we still have tons of any's in the project still.

[liyasthomas]

• TypeScript
• SCSS support
• Pug
• Component Libraries

Since:

• TypeScript support is added
• Already have SCSS support (SASS is no more preferred)
• Pug support and component libraries such as Vuetify, Vue Material Kit is not essential at this stage of development

I'm closing this issue.