@graupl/graupl 1.0.0-beta.10 → 1.0.0-beta.11

package/package.json

@@ -1,8 +1,12 @@
 {
   "name": "@graupl/graupl",
-  "version": "1.0.0-beta.10",
+  "version": "1.0.0-beta.11",
   "description": "A modular and modern CSS framework.",
   "type": "module",
+  "files": [
+    "dist",
+    "scss"
+  ],
   "workspaces": [
     "packages/*"
   ],
@@ -13,21 +17,20 @@
     "prettier": "prettier '**/*.{js,mjs,cjs,scss,sass}'",
     "stylelint": "stylelint '**/*.scss' --allow-empty-input",
     "lint": "npm run eslint -- --fix && npm run stylelint -- --fix && npm run prettier --  --write",
-    "sass": "npm run sass:package && npm-run-all sass:package:*",
-    "sass:package": "rm -rf dist/css/* && sass scss:dist/css --pkg-importer=node",
-    "sass:package:core": "rm -rf packages/core/dist/css/* && sass packages/core/scss:packages/core/dist/css --pkg-importer=node",
-    "sass:package:icons": "rm -rf packages/icons/dist/css/* && sass packages/icons/scss:packages/icons/dist/css --pkg-importer=node",
-    "postcss": "npm run postcss:package && npm-run-all postcss:package:*",
-    "postcss:package": "postcss 'dist/css/**/*.css' --replace",
-    "postcss:package:core": "postcss 'packages/core/dist/css/**/*.css' --replace",
-    "postcss:package:icons": "postcss 'packages/icons/dist/css/**/*.css' --replace",
-    "vite": "npm run vite:package && npm-run-all vite:package:*",
-    "vite:package": "vite build --config vite.config.js",
-    "vite:package:core": "vite build --config packages/core/vite.config.js",
-    "vite:package:icons": "#vite build --config packages/icons/vite.config.js",
+    "presass": "rm -rf dist/css/*",
+    "sass": "sass scss:dist/css --pkg-importer=node",
+    "sass:packages": "npm --workspaces run sass",
+    "postcss": "postcss 'dist/css/**/*.css' --replace --config ./postcss.config.cjs",
+    "postcss:packages": "npm --workspaces run postcss",
+    "css": "npm run sass && npm run postcss",
+    "css:packages": "npm --workspaces run css",
+    "prerolldown": "rm -rf dist/js/*",
+    "rolldown": "rolldown --config ./rolldown.config.js",
+    "rolldown:packages": "npm --workspaces run rolldown",
     "build": "npm-run-all build:*",
+    "build:packages": "npm --workspaces run build",
     "build:css": "npm run sass && npm run postcss",
-    "build:js": "npm run vite",
+    "build:js": "npm run rolldown",
     "postbuild": "npm run docs:build",
     "release": "git add dist/. packages/*/dist/. && commit-and-tag-version -a",
     "prerelease": "npm run lint && npm run build",
@@ -59,7 +62,9 @@
   "devDependencies": {
     "@commitlint/cli": "^19.2.1",
     "@commitlint/config-conventional": "^19.1.0",
+    "@drupal/once": "git+https://git.drupalcode.org/issue/once-3466026.git",
     "@eslint/js": "^9.0.0",
+    "@rollup/plugin-babel": "^6.0.4",
     "autoprefixer": "^10.4.19",
     "chokidar-cli": "^3.0.0",
     "commit-and-tag-version": "^12.5.1",
@@ -78,6 +83,8 @@
     "postcss-cli": "^11.0.0",
     "postcss-discard-comments": "^7.0.0",
     "prettier": "^3.2.5",
+    "rolldown": "^1.0.0-beta.19",
+    "rollup-plugin-esbuild": "^6.2.1",
     "sass": "^1.69.5",
     "stylelint": "^16.3.1",
     "stylelint-config-property-sort-order-smacss": "^10.0.0",
@@ -86,5 +93,8 @@
     "stylelint-prettier": "^5.0.0",
     "vite": "^5.2.8",
     "vitepress": "^1.1.0"
+  },
+  "dependencies": {
+    "@graupl/core": "*"
   }
 }

package/.browserslistrc

@@ -1,3 +0,0 @@
-last 2 versions
-> 0.25%
-not dead

package/.czrc

@@ -1,3 +0,0 @@
-{
-  "path": "cz-conventional-changelog"
-}

package/.devcontainer/devcontainer.json

@@ -1,221 +0,0 @@
-// @see https://github.com/microsoft/vscode-dev-containers/blob/main/containers/docker-existing-docker-compose/.devcontainer/devcontainer.json
-{
-  "name": "Graupl Dev",
-
-  // Update the 'dockerComposeFile' list if you have more compose files or use different names.
-  // The .devcontainer/docker-compose.extend.yml file contains any overrides you need/want to make.
-  "dockerComposeFile": [
-    "../container/docker-compose.yml"
-  ],
-
-  // The 'service' property is the name of the service for the container that VS Code should
-  // use. Update this value and .devcontainer/docker-compose.yml to the real service name.
-  "service": "app",
-
-  // The optional 'workspaceFolder' property is the path VS Code should open by default when
-  // connected. This is typically a file mount in .devcontainer/docker-compose.yml
-  "workspaceFolder": "/var/www/html",
-
-  // Update the path to include vendor/bin and ~/bin
-  // Enable bash history.
-  "remoteEnv": {
-    "PATH": "${containerEnv:HOME}/.vscode-server/bin/**/bin:${containerEnv:PATH}",
-    "PROMPT_COMMAND": "history -a",
-    "HISTFILE": "/commandhistory/.bash_history"
-  },
-
-  // Set *default* container specific settings.json values on container create.
-  "customizations": {
-    "vscode": {
-      "settings": {
-        "breadcrumbs.enabled": true,
-        "better-comments.tags": [
-          {
-            "tag": "!",
-            "color": "#FF2D00",
-            "strikethrough": false,
-            "underline": false,
-            "backgroundColor": "transparent",
-            "bold": false,
-            "italic": false
-          },
-          {
-            "tag": "?",
-            "color": "#3498DB",
-            "strikethrough": false,
-            "underline": false,
-            "backgroundColor": "transparent",
-            "bold": false,
-            "italic": false
-          },
-          {
-            "tag": "//",
-            "color": "#474747",
-            "strikethrough": true,
-            "underline": false,
-            "backgroundColor": "transparent",
-            "bold": false,
-            "italic": false
-          },
-          {
-            "tag": "todo",
-            "color": "#FF8C00",
-            "strikethrough": false,
-            "underline": false,
-            "backgroundColor": "transparent",
-            "bold": false,
-            "italic": false
-          },
-              {
-            "tag": "@todo",
-            "color": "#FF8C00",
-            "strikethrough": false,
-            "underline": false,
-            "backgroundColor": "transparent",
-            "bold": false,
-            "italic": false
-          },
-          {
-            "tag": "*",
-            "color": "#98C379",
-            "strikethrough": false,
-            "underline": false,
-            "backgroundColor": "transparent",
-            "bold": false,
-            "italic": false
-          }
-        ],
-        "css.validate": true,
-        "debug.allowBreakpointsEverywhere": true,
-        "debug.showBreakpointsInOverviewRuler": true,
-        "diffEditor.ignoreTrimWhitespace": false,
-        "drupalSDCHelper.componentDirectories": [
-          "web/themes/custom/*/components/**",
-          "web/modules/custom/*/components/**",
-          "docroot/themes/custom/*/components/**",
-          "docroot/modules/custom/*/components/**",
-          "public_html/modules/custom/*/components/**",
-          "public_html/themes/custom/*/components/**"
-        ],
-        "docker.containers.label": "ContainerName",
-        // @see https: //github.com/microsoft/vscode/issues/174632#issuecomment-1608114637
-        "extensions.verifySignature": false,
-        "editor.autoIndent": "full",
-        "editor.detectIndentation": true,
-        "editor.codeActionsOnSave": {
-          "source.fixAll.eslint": true
-        },
-        "editor.formatOnPaste": true,
-        "editor.formatOnSave": false,
-        "editor.insertSpaces": true,
-        "editor.minimap.maxColumn": 200,
-        "editor.minimap.renderCharacters": false,
-        "editor.renderWhitespace": "boundary",
-        "editor.rulers": [80],
-        "editor.tabSize": 2,
-        "editor.wordWrap": "off",
-        "editor.wordWrapColumn": 80,
-        "flashpost.saveDataToWorkspace": true,
-        "flashpost.workspaceDataRelativePath": "testing/flashpost",
-        "workbench.editor.labelFormat": "medium",
-        "workbench.sideBar.location": "right",
-        "[javascript]": {
-          "editor.defaultFormatter": "esbenp.prettier-vscode"
-        },
-        "[json]": {
-          "editor.defaultFormatter": "esbenp.prettier-vscode"
-        },
-        "[typescript]": {
-          "editor.defaultFormatter": "vscode.typescript-language-features"
-        },
-        "[vue]": {
-          "editor.defaultFormatter": "esbenp.prettier-vscode"
-        },
-        "[yaml]": {
-          "editor.defaultFormatter": "redhat.vscode-yaml"
-        },
-        "files.associations": {
-          ".env.*": "env",
-          "devcontainer.json": "jsonc",
-          "settings.json": "jsonc"
-        },
-        "files.trimTrailingWhitespace": true,
-        "files.insertFinalNewline": true,
-        "html.format.enable": true,
-        "html.format.wrapLineLength": 80,
-        "telemetry.enableTelemetry": false,
-        "todo-tree.regex.regex": "(//|#|<!--|;|/?\\*|^|^[ \\t]*(-|\\d+.))\\s*($TAGS)",
-        "todo-tree.general.tags": ["@todo", "TODO", "FIXME"],
-        "typescript.suggest.paths": false,
-
-        "conventionalCommits.scopes": [
-          "vscode",
-          "ci",
-          "config",
-          "code",
-          "tests",
-          "docs"
-        ],
-
-        "scm.showHistoryGraph": false
-      },
-      // Add the IDs of extensions you want installed when the container is created.
-      "extensions": [
-        /* General VSCode QoL */
-        "DavidAnson.vscode-markdownlint",
-        "mikestead.dotenv",
-        "tyriar.sort-lines",
-
-        /* Git, Build, Debug */
-        "aaron-bond.better-comments",
-        "eamodio.gitlens",
-        "vivaxy.vscode-conventional-commits",
-        "Gruntfuggly.todo-tree",
-        "streetsidesoftware.code-spell-checker",
-
-        /* HTML, JS*/
-        "formulahendry.auto-rename-tag",
-        "christian-kohler.path-intellisense",
-        "dbaeumer.vscode-eslint",
-        "editorconfig.editorconfig",
-        "esbenp.prettier-vscode",
-        "mrmlnc.vscode-scss",
-        "ms-vscode.live-server",
-        "octref.vetur",
-        "shardulm94.trailing-spaces",
-        "stevencl.adddoccomments",
-        "stylelint.vscode-stylelint",
-        "syler.sass-indented",
-        "vivek9patel.vscode-css-compatibility",
-
-        /* Vite */
-        "antfu.vite",
-        "fantasy.vp-preview",
-        "vitest.explorer"
-      ]
-    }
-  },
-
-  "overrideCommand": true,
-
-  // Install npm build tools automatically.
-  "postStartCommand": "test -f /var/www/html/node_modules/.package-lock.json || (npm i -y; npm run build)",
-
-  // Fix permissions on the project directory.
-  "postAttachCommand": "/usr/bin/git config --global --add safe.directory /var/www/html",
-
-  // Use 'forwardPorts' to make a list of ports inside the container available locally.
-  "forwardPorts": [4000, 4001]
-
-  // Uncomment the next line if you want start specific services in your Docker Compose config.
-  // "runServices": [],
-
-  // Uncomment the next line if you want to keep your containers running after VS Code shuts down.
-  // "shutdownAction": "none",
-
-  // Uncomment the next line to run commands after the container is created - for example installing curl.
-  // "postCreateCommand": ""
-
-  // Uncomment to connect as a non-root user if you've added one. See https://aka.ms/vscode-remote/containers/non-root.
-  // "remoteUser": "vscode"
-}

package/.editorconfig

@@ -1,13 +0,0 @@
-root = true
-
-# All files.
-[*]
-end_of_line = LF
-indent_style = space
-indent_size = 2
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-
-[*.md]
-trim_trailing_whitespace = false

package/.env

@@ -1,3 +0,0 @@
-## Docker Compose Settings.
-### N.B. Docker Compose settings must be placed in your workspace root .env as well ###
-COMPOSE_PROJECT_NAME=graupl

package/.github/CODE_OF_CONDUCT.md

@@ -1,73 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at nickdjm+graupl@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq

package/.github/COMMIT_CONVENTION.md

@@ -1,17 +0,0 @@
-# Git Commit Convention
-
-This project uses the conventional commit standard, which means your commits should follow a basic template of:
-
-> \<type>[optional scope]: \<description>
->
-> [optional body]
->
-> [optional footer(s)]
-
-For more detailed information about available types, scopes, breaking changes, etc. please see the [official documentation](https://www.conventionalcommits.org/en/v1.0.0/).
-
-This project also provides a command to assist you in formatting commit messages using [commitizen](https://commitizen.github.io/cz-cli/):
-
-```shell
-npm run commit
-```

package/.github/CONTRIBUTING.md

@@ -1,86 +0,0 @@
-# Contributing to graupl
-
-Whether you want to add a feature or simply report a bug or issue, please have a quick read through these guidelines before contributing.
-
-## Developed with Github
-
-We use github to host code, to track issues and feature requests, as well as accept pull requests. All other forms of communication with maintainers is not considered "official".
-
-## [Github Flow](https://guides.github.com/introduction/flow/index.html) is the Way to Go
-
-All code changes happen through pull requests.
-
-Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
-
-1. Fork the repo and create your branch from 4.x.
-2. Link your pull request to any relavent open issues.
-3. If you've added or changed functionality update the documentation.
-4. Make sure your code functions.
-5. Update existing tests or write a new test to ensure your code will _continue_ to function regardless of future changes.
-6. Make sure your code lints.
-7. Issue the pull request!
-
-## Any contribution you make will be under the ISC License
-
-In short, when you submit code changes, your submissions are understood to be under the same ISC License that covers the project. Feel free to contact the maintainers if that's a concern.
-
-## Report bugs using Github's [issues](https://github.com/Graupl/graupl/issues)
-
-We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/Graupl/graupl/issues/new).
-
-## Write bug reports with detail, background, and sample code
-
-**Great Bug Reports** tend to have:
-
-- A quick summary and/or background
-- Steps to reproduce
-  - Be specific!
-  - Give sample code if you can
-- What you expected would happen
-- What actually happens
-- Notes
-  - why you think this might be happening
-  - stuff you tried that didn't work
-
-Everybody loves a thorough bug report!
-
-## Keep Your Code Consistent
-
-- Run `npm install` to ensure you have all the tools needed.
-- Keep all functional code inside of the `src/` directory.
-- Keep all test code inside of the `tests/` directory.
-- Use the coding standards provided.
-
-This project follows a set of coding standards combining [StandardJS](https://standardjs.com/), [Prettier](https://prettier.io/), and [JSDoc](https://jsdoc.app/) for JavaScript and [Standard SCSS](https://github.com/stylelint-scss/stylelint-config-standard-scss#readme), [Sass Guidelines](https://github.com/bjankord/stylelint-config-sass-guidelines#readme), Prettier, and [SMACSS](https://smacss.com/) for Sass.
-
-To check your code, you can use [ESLint](https://eslint.org/)/[Stylelint](https://stylelint.io/)/Prettier with the provided script:
-
-```shell
-npm run lint
-```
-
-Code that does not follow the linting standards _will not_ be merged.
-
-## Commit Guidelines
-
-This project uses the conventional commit standard, which means your commits should follow a basic template of:
-
-> \<type>[optional scope]: \<description>
->
-> [optional body]
->
-> [optional footer(s)]
-
-For more detailed information about available types, scopes, breaking changes, etc. please see the [official documentation](https://www.conventionalcommits.org/en/v1.0.0/).
-
-This project also provides a command to assist you in formatting commit messages using [commitizen](https://commitizen.github.io/cz-cli/):
-
-```shell
-npm run commit
-```
-
-Commits that do not follow this format _will not_ be merged.
-
-## References
-
-This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,30 +0,0 @@
----
-name: Bug report
-about: Create a report to help us improve
-title: 'Bug: [Brief Description]'
-labels: bug
-assignees: ''
-
----
-
-## Summary
-<!-- What is the issue you are experiencing? -->
-
-## Steps to reproduce
-<!--
-What are the steps to reproduce this issue?
-
-1. Go to "..."
-2. Click on "...."
-3. Scroll down to "...."
-4. See error
--->
-
-## Expected Behaviour
-<!-- What is the expected behaviour? -->
-
-## Screenshots
-<!-- If applicable, add screenshots to help explain your problem. -->
-
-## Additional context
-<!-- Is there anything else that would give context about the problem? -->

package/.github/ISSUE_TEMPLATE/documentation.md

@@ -1,20 +0,0 @@
----
-name: Documentation Issue
-about: Create an issue to help fix or improve documentation
-title: 'Docs: [Brief Description]'
-labels: documentation
-assignees: ''
-
----
-
-## Summary
-<!-- What is the issue you are experiencing? Is something unclear or wrong? A typo perhaps? -->
-
-## Solution
-<!-- Describe the solution you'd like to see. -->
-
-## Alternatives
-<!-- Describe alternatives you've considered. -->
-
-## Additional context
-<!-- Is there anything else that would give context about the problem? -->

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: 'Feat: [Brief Description]'
-labels: enhancement
-assignees: ''
-
----
-
-## Summary
-<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
-
-## Solution
-<!-- Describe the solution you'd like to see. -->
-
-## Alternatives
-<!-- Describe alternatives you've considered. -->
-
-## Additional context
-<!-- Is there anything else that would give context about the problem? -->

package/.github/SECURITY.md

@@ -1,26 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-| Version | Supported          |
-| ------- | ------------------ |
-| 1.x     | ✔                  |
-
-## Reporting a Vulnerability
-
-If you discover a vulnerability within this project, please [open an issue](https://github.com/Graupl/graupl/issues/new) and label it with the `security` tag. The issue board is checked at least 2-3 times a week, so you should expect a response to your issue within a few days.
-
-If a PR is submitted along with the issue to resolve the vulnerability, you can expect it to be reviewed within the same time frame as issue responses. If a PR is not submitted, the time it takes to develop a fix will differ depending on the severity of the vulnerability.
-
-## Vulnerabilities in dependencies
-
-Given that graupl does not have any production dependencies, any vulnerable dev dependencies will be updated when/if possible- though a new release of graupl may not be pushed out right away.
-
-A higher priority will be given to dev dependencies that are directly responsible for compiling the project:
-
-- [sass](https://sass-lang.com),
-- [postcss](https://postcss.org),
-- [vite](https://github.com/vitejs/vite), and
-- all related plugins
-
-If a vulnerability is found and resolved within one of these dependencies, a new release will be made.

package/.github/dependabot.yml

@@ -1,17 +0,0 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-
-version: 2
-updates:
-  - package-ecosystem: "npm" # See documentation for possible values
-    directory: "/" # Location of package manifests
-    schedule:
-      interval: "daily"
-    labels:
-      - "dependencies"
-    reviewers:
-      - "NickDJM"
-    commit-message:
-      prefix: "build"

package/.github/pull_request_template.md

@@ -1,5 +0,0 @@
-## Description
-<!-- Why are you making this pull request? -->
-
-## Related Issues
-<!-- Please provide links to any related issues. -->