#perladevserver — Public Fediverse posts

New Perla release

https://github.com/AngelMunoz/Perla/releases/tag/v1.0.0-beta-019

Thanks to @[email protected] for contributing in this release

#dotnet #perladevserver #fsharp #oss #webdev #devserver

The custom paths feature is almost done, I've been testing it myself (but I'm a bad QA for what I've seen 😅

I'd say a couple of changes more and
https://github.com/AngelMunoz/Perla/pull/123 will get merged so I can release a new beta version soon which will include a contribution from @[email protected] !

#dotnet #fsharp #oss #perladevserver

It's getting there...
You save them on the left, then when you build/serve the top right is generated and you can do what bottom right shows.
To give a little bit more of context, the JSPM generator api doesn't let you do import map installs (adding a new package) when you have trailing slashes (the lit directives in the example above), that and currently custom resolutions are not saved when you do a "regenerate"
So now with paths in the config, you can save custom paths as well as ensuring your import map is generated correctly.
Because we'll regenerate the map and use the latest resolutions from jspm and then we'll add your customizations to the map just before it is saved to disk
I still need to ensure these are marked as external and when they are relative imports we should resolve the path to disk using esbuild's alias feature
--alias:@app/components=./components/exports.js
All in all I'm quite excited about this feature as it will fix some DX issues I harshly faced when porting fantomas-tools to perla and failed on stream 😅
so... yeah we'll fix those

#dotnet #fsharp #esbuild #webdev #perladevserver

New Beta is out! pick it while.... well, whenever you want!

This release refines the setup and 1st run checks experiences as well as hide some of the commands in preview we were not able to do before

https://github.com/AngelMunoz/Perla/releases/tag/v1.0.0-beta-018

#dotnet #fsharp #perlaDevServer #webdev #importmaps

I know I've been quiet about #fsharp and related tweets but between relaxing and giving time to myself and some cool #perlaDevServer updates I find little time for social media.
However! the next version of perla will include a wizard-like experience, the setup will also improve.

The only major change here for users vs the previous betas is that until testing stuff is stable, we won't attempt to install playwright browsers.

It's been a while but I got some feedback thus I had to make this new release of #perlaDevServer
Beta 11 is available in NuGet as well

https://github.com/AngelMunoz/Perla/releases/tag/v1.0.0-beta-011

#fsharp #webdev #dotnet

it might be a stretch but has anyone tried the latest #perlaDevServer previews?

I'm wondering if I'm postponing v1 too much so I'd like to mark the testing commands as experimental and release the rest stuff which I know it is working
any feedback in that area would be appreciated

#fsharp #webdev #dotnet #devserver

If that doesn't help the users I don't know what will do
#perlaDevServer

Kudos for the amazing spectre console project it really eases a lot of my time

Ah so... small updates in #perlaDevServer I finally got to code a little bit on it again, I won't go full free time on it just yet so
I might be fixing a couple of pending issues before I get the v1 out there

mainly the testing commands are not in the best shape ever just yet so I need to take more time to ensure that works just fine

@[email protected] @[email protected] I answered as well a more complete answer directly to the toot above but I'll also add here

In this case, #perlaDevServer is an attempt to bring the usual DX web devs have in the node ecosystem without actually using node (and not exclusive to dotnet either via self-contained binaries) and with more performant tooling but as you may guess the DX is nowhere close to those in node-land feel free to try and send some feedback if you feel like it!

@[email protected] @[email protected] I answered as well a more complete answer directly to the toot above but I'll also add here

In this case, #perlaDevServer is an attempt to bring the usual DX web devs have in the node ecosystem without actually using node (and not exclusive to dotnet either via self-contained binaries) and with more performant tooling but as you may guess the DX is nowhere close to those in node-land feel free to try and send some feedback if you feel like it!

A #SAFE stack sutil flavored version is working with perla v1 betas

https://github.com/AngelMunoz/safe-perla-v1

If you're interested in the #fsharp fable support in #perlaDevServer this can be a good time to check it out, full-stack F# at your disposal, no node required ;)

If you're feeling curious, give it a try and let me know if something is not working that well, have a nice week :)

Also, the perla-templates repository has has a pending PR with the new changes required to get started https://github.com/AngelMunoz/perla-templates/pull/5

Give it a go, add the dev branch templates and spin a new project!

- perla templates:add AngeMunoz/perla-templates dev
- perla new sample perla-templates/fable-sutil

A #SAFE stack sutil flavored version is working with perla v1 betas

https://github.com/AngelMunoz/safe-perla-v1

If you're interested in the #fsharp fable support in #perlaDevServer this can be a good time to check it out, full-stack F# at your disposal, no node required ;)

If you're feeling curious, give it a try and let me know if something is not working that well, have a nice week :)

Also, the perla-templates repository has has a pending PR with the new changes required to get started https://github.com/AngelMunoz/perla-templates/pull/5

Give it a go, add the dev branch templates and spin a new project!

- perla templates:add AngeMunoz/perla-templates dev
- perla new sample perla-templates/fable-sutil

The updated website for #perladevserver is up!

https://perla-docs.web.app

While the docs are still in the works and are not fully up to date, you can see now the updated sections

- Migration Guide -> https://perla-docs.web.app/#/content/migrate
- perla.json reference -> https://perla-docs.web.app/#/v1/docs/reference/perla

The rest of the docs will be updated in the following weeks!
feedback is always welcome

#fsharp #dotnet #webdev #SPA

New #PerlaDevServer beta release

A bunch of bugfixes and json schema updates, feel free to give a try!

https://github.com/AngelMunoz/Perla/releases/tag/v1.0.0-beta-005

#fsharp #dotnet

I guess I just needed to power through it, the json schema is updated in the dev branch so you will get nice information about your current perla config.
Sure, there are deprecation notices but where did those settings move to?
Sadly... I still have docs and samples to update 😭
#perladevserver #jsonschema

Here's another preview for #perlaDevServer
Need to Transform #markdown to #html ?

Well with plugins you may be able to do so!

docs for plugins are still on the way and are fairly more limited than other kind of plugins in the web dev ecosystem but given what we've got and that this can be used outside node... I think we're fairly ok 😅

Don't forget to check the project in github

#dotnet #fsharp

Ahh tomorrow I'll take a break from #PerlaDevServer features and start to revamp docs and the json-schema while the actual breaking changes from the config are not that crazy it is always nice to have some up to date docs that tell you how to do things
It will also allow me to work on a markdown plugin to remove the runtime parsing + extra react code there, I even think perla could be helpful to build static websites as well I need to figure that out🤔

I got my breakthrough at last, testings with both single run and watch mode with headless browsers is finally coming alive in #perlaDevServer the next preview will include these bits
Not finished by any means but I had spent a month or two already trying to make this work

#fsharp #dotnet #webdev #webtooling

If you're into the #SPA and #webdev areas and are looking to remove (or at least depende less on) node from your toolchain I invite you to try the vnext bits from #perlaDevServer

https://github.com/AngelMunoz/Perla/releases/tag/v1.0.0-beta-001


#dotnet #fsharp #csharp

If you're into the #SPA and #webdev areas and are looking to remove (or at least depende less on) node from your toolchain I invite you to try the vnext bits from #perlaDevServer

https://github.com/AngelMunoz/Perla/releases/tag/v1.0.0-beta-001


#dotnet #fsharp #csharp

Things are shaping in Mwahahah

The perla dev server running playwright in #WSL about to report tests when running
perla test --watch

#perlaDevServer #fsharp

Things are shaping in Mwahahah

The perla dev server running playwright in #WSL about to report tests when running
perla test --watch

#perlaDevServer #fsharp

I really like jetbrains #rider EAPs they tend to be very stable; I've been doing my recent #perlaDevServer work with the EAP and the cool simplified new UI and I'm liking it quite a lot

I really like jetbrains #rider EAPs they tend to be very stable; I've been doing my recent #perlaDevServer work with the EAP and the cool simplified new UI and I'm liking it quite a lot

So... between yesterday and today I found out that test projects in Fable might need some extra configuration from the #perlaDevServer side I'm debating myself if I want to go strictly conventions based or if there's a subset of options I can expose here

So... between yesterday and today I found out that test projects in Fable might need some extra configuration from the #perlaDevServer side I'm debating myself if I want to go strictly conventions based or if there's a subset of options I can expose here

Ahhh it was a nice week, a very relaxing one, I needed these vacations more than I would like to admit

I'll try to get back to my #perlaDevServer stuff

Ahhh it was a nice week, a very relaxing one, I needed these vacations more than I would like to admit

I'll try to get back to my #perlaDevServer stuff