Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@area17/a17-boilerplate
Advanced tools
The rebuild of A17 FE Boilerplate.
Highly inspired by kcd-scripts and react-scripts
No more clone. It is an npm package : https://www.npmjs.com/package/@area17/a17-boilerplate
Please see instructions here a17-generator.
Go to the project root, and run:
$ npm install @area17/a17-boilerplate
After the package is installed please run:
$ npx a17-bp init
All avaliable tasks are listed in package.json
file as npm tasks.
A17 FE Boilerplate has a bunch of config files located in the /config
folder. If not specified, A17 FE Boilerplate will use default configurations with it.
Custom configuration is enabled via adding corresponding configuration file in the right place.
For example, place manifest.json
file into the project's frontend folder will have A17 FE Boilerplate use this file instead of the default one in the /config
folder.
That is to say, it works the way that it will look for configuration file or use default. No commands for configuration.
You can configure the main webpack config by creating the following file at the root of your project.
You can customize the entries in the manifest.json but you can also customize the entries using a webpack.all.js file :
const path = require('path');
module.exports = {
entry: {
head: path.resolve('frontend/js/head.js'),
app: path.resolve('frontend/js/app.js'),
main: path.resolve('frontend/scss/app.scss'),
oldbrowser: path.resolve('frontend/scss/html4css.scss')
}
}
In this example, the compiled files will be : head.js, app.js, main.js and oldbrowser.js.
You can override the default browser-sync configuration using a webpack.bs.js file at the root of your project :
module.exports = {
ui: { port: 3001 },
ghostMode: false,
port: 3000,
server: true
};
This will launch a local server listening to localhost:3000, useful to deal wuth static html/CSS/JS files.
Boilerplate runs mustard test in the head of the document to test for basic browser abilities to determine if the browser is modern or not (see head.js). Modern browsers are currently considered to be:
Older browsers will have their JavaScript execution halted and load a fall back HTML4CSS
NB IE11 support will likely be dropped in 2019 with a stricter mustard test.
Currently in no particular order, a list of items currently being discussed/planned.
6.0.0 Breaking change
There are the following tasks only now.
This update bring numerous changes :
The watch task has been simplified. This is only watching for SVG to re-create the icon sprite.
This create quite some changes in the final dist folder : CSS and JS are now created at the root of the dist folder. One important limitation from Webpack : CSS and JS can't have the same name (ie : app.css and app.js are prohibited).
The rev-manifest.json is still created so Laravel can still use it.
5.0.5
5.0.4
5.0.3
5.0.2
5.0.1
{
"config": {
"browsersyncPort": 1312,
"browsersyncUiPort": 1313
}
}
5.0.0
4.1.2
4.1.1
Updated breakpoint
mixin to help generate IE11 and hover based breakpoints
@include breakpoint('medium+') {
// styles to be given to browsers at `medium` and above
}
@include breakpoint(null,'hover') {
// styles to be given to devices with mouse pointers
}
@include breakpoint(null,'ie11') {
// styles to be given to be given to IE11
}
@include breakpoint('medium+','hover') {
// styles to be given to browsers at `medium` and above that have mouse pointers
}
@include breakpoint('medium+','ie11') {
// styles to be given to ie11 at `medium` and above
}
4.1.0
Add a way to specify custom entry points in the webpack config via the manifest :
"scripts": {
"app.js": "js/app.js",
"map.js": "js/map.js",
"head.js": "js/head.js"
}
If no "scripts" are found it will fallback on the js/app.js and the js/head.js file.
4.0.1
4.0.0
3.2.1
3.2.0
3.1.1
3.1
3.0.3
3.0.2
3.0.1
3.0.0-rc.7
3.0.0-rc.6
3.0.0-rc.5
3.0.0-rc.4
icon--
.3.0.0-rc.3
Add non-frontend file watch support. In manifest.json
, just add bs
options to config
like the following example (it is using relative path to the root of frontend
folder):
{
"config": {
"bs" : {
"watchExtra" : [
"./*.php"
]
}
}
}
3.0.0-rc.2
3.0.0-rc.1
3.0.0-beta.8
Clean dist folder before doing a build
Add the rev task : a rev-manifest.json file will be added at the root of the dist folder to map assets with revisioned ones
In dev the rev-manifest.json will look like this npm run build
:
{
"styles/app.css":"styles/app.css",
"styles/html4css.css":"styles/html4css.css",
"scripts/app.js":"scripts/app.js",
"scripts/head.js":"scripts/head.js"
}
In production npm run prod
:
{
"styles/app.css":"styles/app-7ad77318e2.css",
"styles/html4css.css":"styles/html4css-894eb0106a.css",
"scripts/app.js":"scripts/app-e82b5c7421.js",
"scripts/head.js":"scripts/head-b39adeb404.js"
}
3.0.0-beta.7
3.0.0-beta.6
3.0.0-beta.5
3.0.0-beta.4
3.0.0-beta.3
3.0.0-beta.2
3.0.0-beta.1
For publishing to npm, please see this guide.
FAQs
The official AREA 17 boilerplate
The npm package @area17/a17-boilerplate receives a total of 54 weekly downloads. As such, @area17/a17-boilerplate popularity was classified as not popular.
We found that @area17/a17-boilerplate 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
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.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.