Skip to content

Releases: abelljs/abell

abell-v1.0.0-beta.5: Remove node dependencies in Abell runtime to allow abell to run on client-side

06 Nov 15:54
@saurabhdaware saurabhdaware
abell-v1.0.0-beta.5
3e2949b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
abell-v1.0.0-beta.5: Remove node dependencies in Abell runtime to allow abell to run on client-side Latest
Latest

What's Changed

  • feat: remove node dependencies from compiler by @saurabhdaware in #188

    You can now set experimentalAllowClientSide: true which will allow you to import .abell files in client-side code. As the name suggests, this feature is experimental as things like XSS, and other security aspects are not considered so far.

    import { defineConfig } from "abell";

export default defineConfig({
  abell: {
    experimentalAllowClientSide: true
  }
});

Full Changelog: abell-v1.0.0-beta.4...abell-v1.0.0-beta.5

Contributors

saurabhdaware
Assets 2
Loading

[email protected]: Add bun installer and template to create-abell 🌭

29 Oct 18:02
@saurabhdaware saurabhdaware
create-abell-v0.0.20
e0e3d5e
Compare
Choose a tag to compare
[email protected]: Add bun installer and template to create-abell 🌭

What's Changed

  • feat(create-abell): add bun support in create-abell command by @0scvr in #171
  • feat(create-abell): add bun template, and option to skip dep installation by @saurabhdaware in #172

You can now use following command to use bun as package installer and template

npx create-abell@latest --template bun-default --installer bun

Additionally, you can also skip dependency installation now with --installer skip or by selecting skip install in prompt of CLI.

New Contributors

Contributors

saurabhdaware and 0scvr
Assets 2
Loading

1.0.0-beta.4: `--open` flag to open dev-server in browser

21 Oct 19:53
@saurabhdaware saurabhdaware
abell-v1.0.0-beta.4
1409ff8
Compare
Choose a tag to compare
1.0.0-beta.4: `--open` flag to open dev-server in browser

What's Changed

  • feat(abell): add option to open browser on start by @saurabhdaware in #167 
    abell dev --open # opens localhost in browser
  • fix(abell): fs.exists build error in windows by @saurabhdaware in #167

Full Changelog: v1.0.0-beta.3...abell-v1.0.0-beta.4

Contributors

saurabhdaware
Assets 2
Loading

Introducing Abell One Beta 🚀: Low-Level, Framework Agnostic, Vite Powered Static-Site-Generator

20 Oct 13:39
@saurabhdaware saurabhdaware
v1.0.0-beta.3
3a2ab9c
Compare
Choose a tag to compare
Introducing Abell One Beta 🚀: Low-Level, Framework Agnostic, Vite Powered Static-Site-Generator

Check out Abell v1-beta release post at abelljs.org/posts/one
and abelljs.org for all new Abell v1 documentation 🎉

Note: Old docs are moved to v0.abelljs.org

Assets 2
Loading

abell-v1.0.0-alpha.72: Abell is now ESM-only package

18 Oct 15:09
@saurabhdaware saurabhdaware
abell-v1.0.0-alpha.72
6ce17fa
Compare
Choose a tag to compare
abell-v1.0.0-alpha.72: Abell is now ESM-only package Pre-release
Pre-release

What's Changed

  • chore: fix minor README quirks by @yashguptaz in #142

  • feat: make abell esm-only by @saurabhdaware in #143
    Abell is now esm-only which means the vite plugins that you build, can be esm-only as well. Projects already using abell v1 alpha versions will have to add type: "module" to their package.json.

  • fix: ignore nested abell blocks by @saurabhdaware in 6ce17fa
    In earlier versions, if you had nested blocks, it used to throw error and you had to explictly escape the blocks using \{{}} syntax.
    From this version, the nested blocks will be ignored by default. Which means if you have the following code, it will just work now.

    <body>
{{
  '{{ 2 + 1 }}'
}}
</body>

    This now outputs, the string as it is instead of trying to evaluate it.

    <body>{{ 2 + 1 }}</body>

  • feat: Only Inject Hash in Scoped CSS components by @saurabhdaware in 1aae1a2
    The components without scoped CSS will not have abell hash. This will improve the build-times a bit.

New Contributors

  • @yashguptaz made their first contribution in #142

Full Changelog: abell-v1.0.0-alpha.67...abell-v1.0.0-alpha.72

Contributors

saurabhdaware and niyabits
Assets 2
Loading

abell-v1.0.0-alpha.67: Explicit Declaration Block and some Bug Fixes

08 Aug 18:31
@saurabhdaware saurabhdaware
abell-v1.0.0-alpha.67
4ccc09c
Compare
Choose a tag to compare
abell-v1.0.0-alpha.67: Explicit Declaration Block and some Bug Fixes Pre-release
Pre-release

What's Changed

  • Explicit Declarations

    {{
  // declarations
  const a = 3;
}}
<html>
  <body>{{ a }}</body>
</html>
    You can now explicitly declare first block as declaration block without having import in it. Earlier the first block was considered declaration only if it had import mentions.
  • fix: abell's default routing file resolution logic
  • Add documentation to NPM
    NPM has the README file now- https://www.npmjs.com/package/abell/v/1.0.0-alpha.67
  • New command abell clear-cache is added to clear cache
    Currently cache is versioned so haven't seen a usecase but few edge cases might come up in future
  • Output File Path Pattern is configurable now (Untested Feature)
    More details on this in future releases. Some internal changes were made for upcoming feature release

Full Changelog: abell-v1.0.0-alpha.61...abell-v1.0.0-alpha.67

Assets 2
Loading

`one` is the default branch now 🥳, Upgrade from Vite 2 to Vite 3

21 Jun 18:46
@saurabhdaware saurabhdaware
abell-v1.0.0-alpha.61
6c93a0a
Compare
Choose a tag to compare
`one` is the default branch now 🥳, Upgrade from Vite 2 to Vite 3 Pre-release
Pre-release

What's Changed

  • feat: upgrade to vite 3 by @saurabhdaware in #139
    • ~ 12% improvements in larger builds with Vite 3 (Tweet from Patak (Vite's maintainer))
    • Some code changes that unblocks abell from some errors while rendering on edge (Not saying you can use Abell to render on edge now, but maybe in future versions 👀)
  • one is now the default branch for this repository
    This does not mean the code in one branch is stable. The one has been primary working branch for me since last few months so it made sense to make it the default. The main branch won't have any major changes until the v1 is merged into it.

Readme ✨ Aesthetic ✨ Improvements

image image

The readme also supports light mode now 🎉

image

Full Changelog: abell-v1.0.0-alpha.56...abell-v1.0.0-alpha.61

Contributors

saurabhdaware
Assets 2
Loading

abell v1.0.0-alpha.56: Vite Upgrade, Cleaner Generate Logs, Local DX Improvements

21 May 17:30
@saurabhdaware saurabhdaware
abell-v1.0.0-alpha.56
b74b103
Compare
Choose a tag to compare
abell v1.0.0-alpha.56: Vite Upgrade, Cleaner Generate Logs, Local DX Improvements Pre-release
Pre-release

Vite Upgrade

This version upgrades from vite 2.7.13 to vite 2.9.7 and thus comes with all the changes and features related to that. Check out Vite's Changelog

Cleaner Generate Logs

Removed the server generate logs from the terminal since they are irrelevant while building static site

saurabhdaware@Saurabhs-MacBook-Air basic % yarn generate yarn run v1.22.15 $ yarn abell generate $ ../node_modules/.bin/abell generate vite v2.9.7 building for production... ✓ 6 modules transformed. dist/index.html 0.83 KiB dist/assets/index.1579b203.js 0.72 KiB / gzip: 0.41 KiB `npx serve dist` to run static server ✨ Done in 0.85s.

Local DX Improvements

abell

  • Abell now has a local dev-server while working on projects! Inside packages/abell you can run yarn dev to start an auto-reload server that builds abell on every change.
  • You can use the local builds in packages/playground/basic now!

create-abell

  • Inside package/create-abell you can run yarn scaffold that scaffolds a temporary project in scaffold-dir locally. Scaffold is replaced after every command.

Will be writing better CONTRIBUTING.md with these changes once Abell v1 is ready for external contributions

Assets 2
Loading

[create-abell] [v0.0.15]: Package Name Change, New Template, and Tiny Improvements

07 May 14:56
@saurabhdaware saurabhdaware
create-abell-v0.0.15
cfe8f93
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
[create-abell] [v0.0.15]: Package Name Change, New Template, and Tiny Improvements Pre-release
Pre-release

Major Change

create-abell-app will be create-abell after abell v1 release.

This allows users to use following commands now-

# Using yarn
yarn create abell

# Using pnpm
pnpm create abell

# Using npm
npm create abell
npm init abell
npx create-abell # this will be documented in docs

Minor Change

New Default Template! create-abell has v1 template as a default template. It will look something like this-

image

The new template covers topics like-

  • How to add css
  • How to add client-side JS
  • How to write components
  • Routing

There will be more minimal templates in future

Patch Change

Improvements in logs. Every major step will now be described in the logs of create-abell

✔ Enter Name of your project … test
✔ Select Installer › yarn
>> Scaffolding `test` using  `default` template
>> Running `yarn`
✓ test scaffolded successfully
>> cd test and run `yarn dev` to run the dev-server
Assets 2
Loading

v1.0.0-alpha.50 - The Return of the Scoped CSS

16 Apr 08:42
@saurabhdaware saurabhdaware
abell-v1.0.0-alpha.50
0e94828
Compare
Choose a tag to compare
v1.0.0-alpha.50 - The Return of the Scoped CSS Pre-release
Pre-release

Scoped CSS is Back 🎉

In your components, now you can write css like -

// navbar.abell
<nav>
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
  </ul>
</nav>

<style>
ul {
  background-color: #ddd;
}
</style>

And it will be scoped for this particular component by default. The ul tags outside of the navbar component will not get these styles.

This is an experimental version of scoped CSS and this one will directly inline the CSS into HTML. In future versions, the bundling of CSS files will improve.

You can also opt out of this by adding scoped="false" to style tag <style scoped="false">.

Thoughts Behind the Decision

So I've been trying to keep abell minimal and close to HTML, CSS, JS setup. I've been treating CSS scoping as an enhancement which can be done using third-party libraries. However, while rebuilding the https://blog.saurabhdaware.in in new Abell I realized, CSS is really messy to write in vanilla setup and thus in Abell.

How we write CSS plays a major role in the DX of the frontend development. There are a few third-party solutions like https://stitches.dev/ that can be used with Abell however it might take some time for them to get some traction in the ecosystem and the setup with Abell is not super straightforward. There isn't any obvious framework-agnostic CSS solution in the ecosystem right now.

Thus it felt necessary to have out-of-the-box CSS scoping in Abell which improves the overall DX of writing and scaling CSS. People will still have an option of ignoring this feature and using third-party without a problem.

We might also get a native CSS scoping solution in CSS (Draft Proposal for CSS Scoping) which I can later leverage in future versions.

Will be improving over this implementation in future updates :D

Assets 2
Loading