githubcnx / githubcnx Goto Github PK
View Code? Open in Web Editor NEWSystem for me
License: The Unlicense
System for me
License: The Unlicense
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
@roots/bud (source) | 6.6.9 -> 6.7.1 |
||||
@roots/bud-tailwindcss | 6.6.9 -> 6.7.1 |
||||
@roots/sage | 6.6.9 -> 6.7.1 |
v6.7.1
v6.7.0
A healthy mix of features and fixes.
There are changes to the API of @roots/bud-imagemin to be aware of if you are using that extension and have customized generators or minimizers.
This is a cool feature.
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using @js
/@endjs
syntax (with whatever extension).
Example:
index.blade.php
:
@​include('sections.header')
<main id="main" class="main">
@​yield('content')
</main>
<img src=@​asset('images/404.png?as=webp') />
<img src=@​asset('images/404.png?as=webp&width=200') />
@​hasSection('sidebar')
<aside class="sidebar">
@​yield('sidebar')
</aside>
@​endif
@​include('sections.footer')
@​js
import {render} from '@​scripts/render'
render(
<h1>Hello, world!</h1>,
document.getElementById('target-el')
);
@​endjs
@​css
@​import 'tailwindcss/base';
@​import 'tailwindcss/components';
@​import 'tailwindcss/utilities';
body {
@​apply bg-blue-500;
}
@​endcss
bud.config.js
:
bud.entry({
index: ['views/index']
})
Included in this PR (sources/@​roots/blade-loader/vendor
) are directives that can be used to stop src from rendering (uses ob_start
and ob_end_clean
).
I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
{{--
@​js
console.log('not visible')
@​endjs
--}}
If you use @roots/bud-imagemin you can now do image manipulation on-the-fly in blade templates:
<div class="test">
<img src=@​asset('images/foo.png?as=webp&width=100&height=100') alt="foo image" />
</div>
WordPress dependencies which are imported are not included in entrypoints.json
. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:
@​js
import {render} from '@​scripts/render'
render(...)
@​endjs
// @​scripts/render.js
import React from 'react'
import {render} from 'react-dom'
export {React, render}
Fixes issues in some setups where blocks would be registered more than once.
Fixes two related issues which caused the --cwd
/--basedir
flag to not work properly
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
squoosh was abandoned by google. we're using sharp internally now. See the PR for details. API changes are documented on bud.js.org.
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
bud.hooks.on(`build.module.rules.oneOf`, (rules = []) => {
rules.push({
test: /\.example$/,
use: [
{
loader: `babel-loader`,
options: {
presets: [`@babel/preset-env`],
},
},
],
})
return rules
})
Fixes #1986.
Reproduction incorporated into testing suite to prevent future regressions.
v6.6.10
Breaks the bud.wpjson
feature from @roots/sage
into two extensions and a webpack plugin to be combined as needed in projects. @roots/sage
now includes these extensions as part of the preset it provides. See the PR for details.
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
Better defines peer dependencies. This should hep guarantee a flat node_modules
and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).
Associated PRs:
Now automatically pulling contributors from git history and crediting in each package's manifest. Thanks to everyone!
v6.7.1
v6.7.0
A healthy mix of features and fixes.
There are changes to the API of @roots/bud-imagemin to be aware of if you are using that extension and have customized generators or minimizers.
This is a cool feature.
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using @js
/@endjs
syntax (with whatever extension).
Example:
index.blade.php
:
@​include('sections.header')
<main id="main" class="main">
@​yield('content')
</main>
<img src=@​asset('images/404.png?as=webp') />
<img src=@​asset('images/404.png?as=webp&width=200') />
@​hasSection('sidebar')
<aside class="sidebar">
@​yield('sidebar')
</aside>
@​endif
@​include('sections.footer')
@​js
import {render} from '@​scripts/render'
render(
<h1>Hello, world!</h1>,
document.getElementById('target-el')
);
@​endjs
@​css
@​import 'tailwindcss/base';
@​import 'tailwindcss/components';
@​import 'tailwindcss/utilities';
body {
@​apply bg-blue-500;
}
@​endcss
bud.config.js
:
bud.entry({
index: ['views/index']
})
Included in this PR (sources/@​roots/blade-loader/vendor
) are directives that can be used to stop src from rendering (uses ob_start
and ob_end_clean
).
I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
{{--
@​js
console.log('not visible')
@​endjs
--}}
If you use @roots/bud-imagemin you can now do image manipulation on-the-fly in blade templates:
<div class="test">
<img src=@​asset('images/foo.png?as=webp&width=100&height=100') alt="foo image" />
</div>
WordPress dependencies which are imported are not included in entrypoints.json
. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:
@​js
import {render} from '@​scripts/render'
render(...)
@​endjs
// @​scripts/render.js
import React from 'react'
import {render} from 'react-dom'
export {React, render}
Fixes issues in some setups where blocks would be registered more than once.
Fixes two related issues which caused the --cwd
/--basedir
flag to not work properly
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
squoosh was abandoned by google. we're using sharp internally now. See the PR for details. API changes are documented on bud.js.org.
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
bud.hooks.on(`build.module.rules.oneOf`, (rules = []) => {
rules.push({
test: /\.example$/,
use: [
{
loader: `babel-loader`,
options: {
presets: [`@babel/preset-env`],
},
},
],
})
return rules
})
Fixes #1986.
Reproduction incorporated into testing suite to prevent future regressions.
v6.6.10
Breaks the bud.wpjson
feature from @roots/sage
into two extensions and a webpack plugin to be combined as needed in projects. @roots/sage
now includes these extensions as part of the preset it provides. See the PR for details.
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
Better defines peer dependencies. This should hep guarantee a flat node_modules
and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).
Associated PRs:
Now automatically pulling contributors from git history and crediting in each package's manifest. Thanks to everyone!
v6.7.1
v6.7.0
A healthy mix of features and fixes.
There are changes to the API of @roots/bud-imagemin to be aware of if you are using that extension and have customized generators or minimizers.
This is a cool feature.
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using @js
/@endjs
syntax (with whatever extension).
Example:
index.blade.php
:
@​include('sections.header')
<main id="main" class="main">
@​yield('content')
</main>
<img src=@​asset('images/404.png?as=webp') />
<img src=@​asset('images/404.png?as=webp&width=200') />
@​hasSection('sidebar')
<aside class="sidebar">
@​yield('sidebar')
</aside>
@​endif
@​include('sections.footer')
@​js
import {render} from '@​scripts/render'
render(
<h1>Hello, world!</h1>,
document.getElementById('target-el')
);
@​endjs
@​css
@​import 'tailwindcss/base';
@​import 'tailwindcss/components';
@​import 'tailwindcss/utilities';
body {
@​apply bg-blue-500;
}
@​endcss
bud.config.js
:
bud.entry({
index: ['views/index']
})
Included in this PR (sources/@​roots/blade-loader/vendor
) are directives that can be used to stop src from rendering (uses ob_start
and ob_end_clean
).
I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
{{--
@​js
console.log('not visible')
@​endjs
--}}
If you use @roots/bud-imagemin you can now do image manipulation on-the-fly in blade templates:
<div class="test">
<img src=@​asset('images/foo.png?as=webp&width=100&height=100') alt="foo image" />
</div>
WordPress dependencies which are imported are not included in entrypoints.json
. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:
@​js
import {render} from '@​scripts/render'
render(...)
@​endjs
// @​scripts/render.js
import React from 'react'
import {render} from 'react-dom'
export {React, render}
Fixes issues in some setups where blocks would be registered more than once.
Fixes two related issues which caused the --cwd
/--basedir
flag to not work properly
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
squoosh was abandoned by google. we're using sharp internally now. See the PR for details. API changes are documented on bud.js.org.
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
bud.hooks.on(`build.module.rules.oneOf`, (rules = []) => {
rules.push({
test: /\.example$/,
use: [
{
loader: `babel-loader`,
options: {
presets: [`@babel/preset-env`],
},
},
],
})
return rules
})
Fixes #1986.
Reproduction incorporated into testing suite to prevent future regressions.
v6.6.10
Breaks the bud.wpjson
feature from @roots/sage
into two extensions and a webpack plugin to be combined as needed in projects. @roots/sage
now includes these extensions as part of the preset it provides. See the PR for details.
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
Better defines peer dependencies. This should hep guarantee a flat node_modules
and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).
Associated PRs:
Now automatically pulling contributors from git history and crediting in each package's manifest. Thanks to everyone!
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.
Originally posted by @renovate in roots/sage#3106
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.