![Create React App Officially Deprecated Amid React 19 Compatibility Issues](https://cdn.sanity.io/images/cgdhsj6q/production/04fa08cf844d798abc0e1a6391c129363cc7e2ab-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Create React App Officially Deprecated Amid React 19 Compatibility Issues
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.
@texastribune/queso-tools
Advanced tools
Node task runners for compiling CSS, creating SVGs, and more.
This repo accompanies our CSS+icons framework, queso-ui
. Use the the task runners here, to compile the assets in that framework.
npm install @texastribune/queso-tools --save-dev
or
yarn add @texastribune/queso-tools --dev
modules | params |
---|---|
styles | dirs , manifest (manifest is optional if you want files with hashed names) |
icons | dirs |
copy | dirs |
Most of the tasks expect an array of directories or files with an input, in:
key, and output, out:
key.
To set this up, create a file called paths.js
and declare your map of paths.
Example:
// paths.js
const SCSS_DIR = './scss';
const CSS_OUTPUT_DIR = './css/';
const SVG_LIB_DIR = './node_modules/@texastribune/queso-ui/icons/base';
const SVG_OUTPUT_DIR = './templates/includes';
const CSS_MAP = [
{
in: `${SCSS_DIR}/styles.scss`,
out: CSS_OUTPUT_DIR,
},
{
in: `${SCSS_DIR}/styles2.scss`,
out: CSS_OUTPUT_DIR,
},
];
// The "in" key for icons should be an array; you can mix and match icons from @texastribune/queso-ui and some stored locally
const SVG_MAP = [
{
in: [
`${SVG_LIB_DIR}/twitter.svg`,
`${SVG_LIB_DIR}/facebook.svg`,
'./icons/custom-icon.svg',
'./icons/other-icon.svg'
],
out: `${SVG_OUTPUT_DIR}/my-svg-sprite.html`,
},
];
// copy contents of a directory into another directory
// and/or copy a directory/file into another-directory/file
const COPY_MAP = [
{
in: SVG_LIB_DIR,
out: SVG_OUTPUT_DIR,
},
{
in: `${SVG_LIB_DIR}/twitter.svg`,
out: `${SVG_OUTPUT_DIR}/twitter.svg`,
},
];
// use if you'd like the outputted CSS to have hashed file names
const MANIFEST_FILE = `${CSS_OUTPUT_DIR}styles.json`;
module.exports = {
CSS_MAP,
SVG_MAP,
MANIFEST_FILE,
COPY_MAP
};
Now create a build.js
file in that same folder where you'll reference these paths and begin to call the various tasks in this package.
That could look something like the following:
// build.js
const { styles, icons, copy } = require('@texastribune/queso-tools');
const { CSS_MAP, MANIFEST_FILE, SVG_MAP, COPY_MAP } = require('./paths');
async function build() {
await styles(CSS_MAP, MANIFEST_FILE);
// OR (use await if you had to glob to get your map)
// const stylesArr = await CSS_MAP();
// await styles(stylesArr, MANIFEST_FILE);
await icons(SVG_MAP);
await copy(COPY_MAP);
}
build()
.catch((err) => {
// eslint-disable-next-line no-console
console.error(err.message);
process.exit(1);
});
Now run node build.js
in your local environment to fire the build script.
Make sure you're authenticated for npm publishing.
npm login
- then follow the promptsnpm run release
FAQs
Node task runners for common front-end tasks
The npm package @texastribune/queso-tools receives a total of 2 weekly downloads. As such, @texastribune/queso-tools popularity was classified as not popular.
We found that @texastribune/queso-tools demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.