Skip to content

Releases: spacenectar/builda-app

V5 - The prefab release!

19 Jul 13:04
0d0792d
Compare
Choose a tag to compare

This is a major Builda release which introduces Prefabs (see readme.md in the repo for more information)

breaking changes.

  • The old builda config files no longer exist, instead your config should live inside a builda object in package.json
  • Modules (blueprints and prefabs) no longer use the files folder structure and now use module instead - this will only effect module creators

v4 - The scaffold release

22 Aug 21:42
Compare
Choose a tag to compare

v4: Builda

Welcome to Builda; this is the new version of the old Buildcom package, which is no longer supported.

Please see the README file for more information.

What's Changed

Full Changelog: 2.0.0...v4.0.0

v4 Alpha release - for testing only

18 Aug 16:15
Compare
Choose a tag to compare
Pre-release

This new application was built to succeed buildcom.

It is currently in alpha, so the documentation is incomplete, and the package is not yet stable. It is published only for testing purposes, and you are advised not to use it yet.

V3

26 Apr 15:58
Compare
Choose a tag to compare
V3

What's Changed

Full Changelog: 2.0.0...3.0.0

V2

28 Mar 19:11
c89b04c
Compare
Choose a tag to compare
V2

What's Changed

Full Changelog: 0...2.0.0

Refinements release

01 Jun 17:16
11056b0
Compare
Choose a tag to compare

🚀 ## Overview:
Makes several refinements to the scaffolding resulting in a cleaner output of the component

🤔 ## Reason:
There were many outdated and poor practice paradigms used in the old scaffold. This fixes those

🔨## Work carried out:

  • Removes .d.ts files for stylesheets (see notes)
  • Removes composes from stylesheets in favour of pure CSS or mixins
  • Replaces react-test-renderer with @testling-library/react
  • Adds a better default readme file.

📝 ## Breaking changes
I removed the .d.ts files from being automatically generated as they should be generated by your application and do not need to be created here. If you were relying on them and your application does not generate these files then you can get around this issue by deleting all instances of the stylesheet .d.ts files and adding a styles.d.t.s to the root of your project with the following content:

declare module '*.scss' {
  const styles: { [className: string]: string };
  export default styles;
}```

Don't forget to replace scss with the stylesheet extension you use and ensure that you add your new file to the includes section of your projects tsconfig.json file.

First stable release

16 Feb 20:05
Compare
Choose a tag to compare

This release has code coverage for all the major functions so I am confident it is stable.