search

Active-CSS / active-css

The epic event-driven browser language for UI with functionality in one-liner CSS. Over 100 incredible CSS commands for DOM manipulation, ajax, reactive variables, single-page application routing, and lots more. Could CSS be the JavaScript framework of the future?
https://activecss.org
Other
43 stars 7 forks source link

Separate build code from release repo #316

Closed bob2517 closed 10 months ago

bob2517 commented 1 year ago

Don't need those pesky security issues from code I didn't write, and which have no implications on the ACSS build. They can strike at any time and have no bearing on anything to do with ACSS, other than the test suite.

To replace Node I need the following:

1) A minifier. 2) A JS linter (Ultraedit may or may not have a linter - need to check [edit - yes it does]). 3) A test framework utilising a headless browser (may be a bit more tricky to solve - dunno if there is a non-Node way to do this yet). 4) A Grunt equivalent that would otherwise handle these steps.

If I can get rid of 1, 2 though, and minimise the process needed in Grunt, that would be a start and may even remove some of the Node dependency issues. Remember to put any Grunt replacement shell/code setups into the project itself.

bob2517 commented 1 year ago

Will probably do this as part of the v3 upgrade.

bob2517 commented 1 year ago

Worth looking at Deno. It may solve the issues that I'm having with Node. It's possible it all could be done on there.

bob2517 commented 1 year ago

For now, rather than doing the ultimate thing which would be to extract the build steps for the core out of Node and get total control, put the build code into a separate build repo. Keep only the compiled source files in the main repo. Leave enhancement issues in the build area, and only have actual bug issues in the main repo. This will make it clear that there are no dependencies in the ACSS core, and the current issues in the main repo will only show known bugs.

bob2517 commented 1 year ago

Note to self: the offline CI pipeline that ties into the docs site will need tweaking to span repos to auto-update everything at build time. That's a tweak to both the docs and core build areas.