You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there, here we go at last, the vnext branch has been merged into dev and this means a couple of things, first of all, new bug fixes and feature request will go into the dev branch and will be released with v1 once it is stable enough!
While this won't be a full comprehensive set of changes between versions, I'll try to highlight what to expect for perla vnext
perla.jsonc simplification
there were a couple of redundant options in the perla config file, this led to hacky workarounds in the codebase which led to more fragile changes between point and patch releases. This has not been updated in the perla.schema.json.
CLI API, the CLI API has changed and has a couple of breaking changes
Local User Perla Files
Files like templates and the esbuild binary will now be downloaded to the local user's app data directory (or *nix equivalent) this will help to persist templates and other functionality accross perla version upgrades (which were broken each time you upgraded before)
Plugins
This is the main driver change for the v1 version, plugins are now a possibility which can be useful to build files other than JS/HTML/CSS and esbuild blessed files (ts/jsx/tsx) so if you're a user of sass files, then you may now be able to build an fsx plugin to transform these into CSS! more details to come soon!
Prod and Dev dependencies!
You can now run Perla in dev/prod modes, this will tell perla to generate an appropiate import map, this can help for cases where you want to load a library that can enable a browser extension to introspect your code, or to run testing code and similar things.
The package management dependency management has now been revamped to make further use of the JSPM Generator API which we were using before but... in a very loosely manner, the support is now in better shape.
Client-Side Tests
This feature is highly experimental at the moment and may be subject to change as it is not sable yet but with the help of mocha and playwright we now have a test runner integrated in perla, this will help you run tests against real browsers like chromium/firefox/webkit/chrome/edge so you will also be aware if certain browser feature, you're using is supported or not while testing not until your code hits production.
The options and settings in this area are not set in stone yet, but if you want to use these, it would be nice to receive feedback
New Packages
Perla.PackageManager.1.0.0-beta-001
Do you want to use importmaps in your projects for some reason? (Perhaps even for aspnet middleware?), then this library is for you it will help you resolve import maps using the JSPN Generator API
Perla.Plugins.1.0.0-beta-001
The Package that contains the types necessary to expose plugins to perla
There's still more to come but for the moment, this is what I can share with you. Please give it a shot if you are feeling adventurous check the sample and docs directories for further examples of the new perla configuration files and other options, also the vscode run configurations and project settings for rider/vs2022 have also been updated so you should be able to also view how to debug certain actions if you face a bug somewhere
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What's Changed
Hey there, here we go at last, the vnext branch has been merged into
dev
and this means a couple of things, first of all, new bug fixes and feature request will go into the dev branch and will be released with v1 once it is stable enough!While this won't be a full comprehensive set of changes between versions, I'll try to highlight what to expect for perla vnext
perla.jsonc
simplificationthere were a couple of redundant options in the perla config file, this led to hacky workarounds in the codebase which led to more fragile changes between point and patch releases. This has not been updated in the
perla.schema.json
.CLI API, the CLI API has changed and has a couple of breaking changes
Local User Perla Files
Files like templates and the esbuild binary will now be downloaded to the local user's app data directory (or *nix equivalent) this will help to persist templates and other functionality accross perla version upgrades (which were broken each time you upgraded before)
Plugins
This is the main driver change for the v1 version, plugins are now a possibility which can be useful to build files other than JS/HTML/CSS and esbuild blessed files (ts/jsx/tsx) so if you're a user of sass files, then you may now be able to build an fsx plugin to transform these into CSS! more details to come soon!
Prod and Dev dependencies!
You can now run Perla in dev/prod modes, this will tell perla to generate an appropiate import map, this can help for cases where you want to load a library that can enable a browser extension to introspect your code, or to run testing code and similar things.
The package management dependency management has now been revamped to make further use of the JSPM Generator API which we were using before but... in a very loosely manner, the support is now in better shape.
Client-Side Tests
This feature is highly experimental at the moment and may be subject to change as it is not sable yet but with the help of mocha and playwright we now have a test runner integrated in perla, this will help you run tests against real browsers like chromium/firefox/webkit/chrome/edge so you will also be aware if certain browser feature, you're using is supported or not while testing not until your code hits production.
The options and settings in this area are not set in stone yet, but if you want to use these, it would be nice to receive feedback
New Packages
Perla.PackageManager.1.0.0-beta-001
Do you want to use importmaps in your projects for some reason? (Perhaps even for aspnet middleware?), then this library is for you it will help you resolve import maps using the JSPN Generator API
Perla.Plugins.1.0.0-beta-001
The Package that contains the types necessary to expose plugins to perla
There's still more to come but for the moment, this is what I can share with you. Please give it a shot if you are feeling adventurous check the
sample
anddocs
directories for further examples of the new perla configuration files and other options, also the vscode run configurations and project settings for rider/vs2022 have also been updated so you should be able to also view how to debug certain actions if you face a bug somewhereFull Changelog: v0.24.1...v1.0.0-beta-001
This discussion was created from the release VNext Here we go!.
Beta Was this translation helpful? Give feedback.
All reactions