Pastrami 1 - Visually an h1, but semantically a paragraph.
\n\nPastrami 2 - Visually an h2, but semantically a paragraph.
\n\nPastrami 3
\nPastrami 4
\nPastrami 5
\nPastrami 6
\n\n","lang":"html","description":"Demonstrates how to include and use the Basscss type scale utility classes in an HTML document to apply consistent font sizes to various elements."},"warnings":[{"fix":"Ensure `basscss-type-scale` is explicitly included in your project's CSS imports or HTML `` tags, separate from any `base-typography` imports.","message":"In Basscss v7.0.0, the `type-scale` module was separated from `base-typography`. If you were relying on it being implicitly included with `base-typography` in earlier Basscss versions, you must now explicitly import or link `basscss-type-scale` as a standalone module.","severity":"breaking","affected_versions":">=7.0.0"},{"fix":"This package is for CSS inclusion only. Include it via CSS `@import`, `` tag, or through a build tool's CSS loader, not as a JavaScript module.","message":"`basscss-type-scale` provides only CSS utility classes for font sizing. It has no JavaScript API or exports. Attempts to `import { ... } from 'basscss-type-scale'` for JavaScript symbols will result in errors.","severity":"gotcha","affected_versions":">=1.0.0"},{"fix":"Plan for long-term stability and minimal maintenance. Do not expect new features or active development beyond critical bug fixes, if any.","message":"Basscss v8, which is the foundational project for this module, is explicitly declared as 'feature complete' and the 'final version' as of February 2016. This means `basscss-type-scale` should be considered extremely stable but will not receive new features or significant updates.","severity":"gotcha","affected_versions":">=1.0.0"},{"fix":"Use utility classes to augment semantic HTML where appropriate (e.g., `` tag) can lead to potential accessibility issues if screen readers or assistive technologies rely on the semantic structure rather than visual styling.","severity":"gotcha","affected_versions":">=1.0.0"},{"fix":"Be mindful of CSS specificity. Ensure Basscss styles are loaded after any base resets or custom styles you intend for it to override, or use more specific selectors in your custom CSS if overriding Basscss is desired. Avoid using contextual or nested selectors to maintain low specificity.","message":"Basscss and its modules like `basscss-type-scale` are designed with low selector specificity. Mixing with other CSS frameworks or custom styles that have higher specificity can lead to unexpected style overrides or styles not applying as intended.","severity":"gotcha","affected_versions":">=1.0.0"}],"env_vars":null,"last_verified":"2026-04-19T00:00:00.000Z","next_check":"2026-07-18T00:00:00.000Z","problems":[{"fix":"Ensure `basscss-type-scale` is installed (`npm install basscss-type-scale` or `yarn add basscss-type-scale`). Verify the exact path to the CSS file in your `node_modules` directory and update your import statement accordingly (e.g., `import 'basscss-type-scale/css/basscss-type-scale.css';`).","cause":"The `basscss-type-scale` package is either not installed, or the import path for its CSS file is incorrect.","error":"Module not found: Error: Can't resolve 'basscss-type-scale' in '...' OR Can't resolve 'basscss-type-scale/css/basscss-type-scale.css' in '...'"},{"fix":"Install the necessary CSS loaders (`npm install --save-dev css-loader style-loader`) and configure your build tool (e.g., `webpack.config.js`) to use them for `.css` files.","cause":"Your build tool (e.g., Webpack, Parcel) is encountering a CSS file but does not have a configured loader (like `css-loader` and `style-loader`) to process it.","error":"You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders"},{"fix":"Inspect the element in browser developer tools to check if the class is present and if its styles are being overridden. Ensure the `basscss-type-scale` stylesheet is correctly linked/imported and loaded after any default browser styles or conflicting global styles. Double-check class names for typos.","cause":"This is likely due to CSS specificity conflicts, incorrect class names, or the stylesheet not being loaded in the browser.","error":"CSS classes (e.g., .h1, .h2) from basscss-type-scale are not applying their styles in the browser."}],"ecosystem":"npm"}