A modular multilingual CMS built with Laravel 5.

Overview

Latest Version Build Status Software License Total Downloads Total Downloads Total Downloads PHP7 Compatible

AsgardCMS Platform

View the documentation at AsgardCMS.com/docs.

Join the conversation on Slack Slack

License

The AsgardCMS is open-sourced software licensed under the MIT license.

Comments
  • Upgrade to Laravel 6

    Upgrade to Laravel 6

    This is more of a checklist for me than anything, but anyone can contribute if I missed something.

    https://laravel.com/docs/6.0/upgrade

    • [ ] Update modules for 6.0 compatibility
    • [ ] Update asgardcms/platform
    • [ ] orchestra/testbench
    • [ ] phpunit
    • [x] finally get rid of that filesystem test that always fails

    Used packages:

    • [ ] floatingpoint/stylist
    • [ ] cartalyst/sentinel
    • [ ] nwidart/laravel-modules
    • [ ] laravelcollective/html
    • [ ] laracasts/presenter
    • [x] dimsav/laravel-translatable => astrotomic/laravel-translatable #771
    • [ ] mcamara/laravel-localization
    • [ ] maatwebsite/laravel-sidebar
    • [ ] intervention/image
    • [ ] nwidart/laravel-menus
    • [ ] typicms/nestablecollection
    • [ ] baryvdh/laravel-debugbar
    • [ ] maatwebsite/laravel-excel
    • [ ] league/csv
    • [ ] symfony/yaml
    • [ ] tightenco/ziggy
    • [ ] venturecraft/revisionable

    For laravel-translatable, here's an "upgrade guide": https://docs.astrotomic.info/laravel-translatable/changelog#v-11-0-0

    For me for later: https://twitter.com/stefanbauerme/status/1170092375894626304

    ~~Replace unmaintained Predis with PhpRedis: https://github.com/phpredis/phpredis/blob/develop/INSTALL.markdown~~ Predis has been revived.

    opened by mikemand 50
  • v3.3 Icons not showing in backend panel

    v3.3 Icons not showing in backend panel

    Summary of issue

    Icons are not showing in admin panel. Some error are showing in the Console.

    chrome_2017-11-14_15-17-22

    Steps to reproduce

    Install a fresh Asgard v3.3 and visit the backend admin panel.

    System Details

    • Operating System: Windows 10 Pro
    • PHP Version: 7.1.6
    • Laravel Version: 5.5.x
    • Asgardcms/Platform version: 3.3.x
    Help Wanted 
    opened by a-h-abid 34
  • Menu doesn't appear in template

    Menu doesn't appear in template

    Followed instructions here:

    https://asgardcms.com/en/docs/menu-module/managing-menus

    Menu is referenced in views/partials/navigation.blade.php as the default {!! Menu::get('main') !!} and menu added as per below:

    screen shot 2015-06-09 at 11 11 06

    ...however menu fails to appear in front end.

    Bug - Confirmed 
    opened by seanthepottingshed 25
  • Media grid (upload popup) needs serverside pagination - Performance issue)

    Media grid (upload popup) needs serverside pagination - Performance issue)

    Summary of issue

    Media grid (upload popup) needs serverside pagination

    I have uploaded about 10,000 medias on my app. This made the upload page slow that I had to wait about 30 seconds

    Steps to reproduce

    System Details

    • Operating System
    • PHP Version
    • Laravel Version
    • Asgardcms/Platform version
    Feature - Accepted 
    opened by darron1217 23
  • Tab header translation issue

    Tab header translation issue

    Summary of issue

    When the lang file doesn't have the key, the tab will only show the original key in the header instead of utilize translation module to show the value.

    In file form-tab-headers.blade.php line 19.

    So, should it utilize translation module?

    opened by riseno 22
  • WIP: Laravel upgrade 5.8

    WIP: Laravel upgrade 5.8

    Changes to bump the laravel version to 5.8.

    We do have failing tests for following modules: Setting, Menu and Media If anyone got an idea on failing test case for above module, please comment.

    but despite of having the failing tests, php artisan serve runs the website smoothly. I have tested core modules including Setting, Menu, Page - front-end flow, Login, Forgot Password etc...

    Regards, Daksh

    opened by dakshhmehta 21
  • Media upload error

    Media upload error

    After upload image new last version of code

    Method [validateMaxSize] does not exist.
    vendor/laravel/framework/src/Illuminate/Validation/Validator.php#2676
    BadMethodCallException
                return $this->callExtension($rule, $parameters);
            }
    
            throw new BadMethodCallException("Method [$method] does not exist.");
        }
    }
    

    I have default asgard.media.config.php And i uploaded image ~100 kb (max 5 mb) All uploaded images with fail

    opened by ruscon 20
  • Module permission not updating

    Module permission not updating

    Hi,

    I am having trouble updating the permissions for one of my modules. I extended with a additional permission. The permission doesn't show up on the backend.

    Previously I could fixed that by running composer autoload but for some reason on the live server it won't work. Any idea how I can refresh the permission list for the module?

    Cheers Olaf

    opened by nolafs 19
  • Cannot read property 'split' of undefined

    Cannot read property 'split' of undefined

    Summary of issue

    Cannot display permissions tab in Admin/ backend for a User Role

    Steps to reproduce

    1. Select A User or User Role
    2. Select the permissions tab

    app.js:1312 [Vue warn]: Error in render: "TypeError: Cannot read property 'split' of undefined"

    found in

    ---> at Modules/User/Assets/js/components/AsgardPermissions.vue at Modules/User/Assets/js/components/RoleForm.vue warn @ app.js:1312 logError @ app.js:2445 globalHandleError @ app.js:2440 handleError @ app.js:2429 Vue._render @ app.js:5208 updateComponent @ app.js:3497 get @ app.js:3847 run @ app.js:3924 flushSchedulerQueue @ app.js:3686 (anonymous) @ app.js:2545 flushCallbacks @ app.js:2466 Promise.then (async) microTimerFunc @ app.js:2514 nextTick @ app.js:2558 queueWatcher @ app.js:3773 update @ app.js:3914 notify @ app.js:1418 reactiveSetter @ app.js:1743 proxySetter @ app.js:4005 (anonymous) @ app.js:112509 Promise.then (async) fetchPermissions @ app.js:112507 boundFn @ app.js:925 mounted @ app.js:112521 callHook @ app.js:3627 insert @ app.js:4822 invokeInsertHook @ app.js:6596 patch @ app.js:6815 Vue._update @ app.js:3369 updateComponent @ app.js:3497 get @ app.js:3847 Watcher @ app.js:3836 mountComponent @ app.js:3504 Vue$3.$mount @ app.js:9161 Vue$3.$mount @ app.js:11522 Vue._init @ app.js:5302 Vue$3 @ app.js:5391 (anonymous) @ app.js:49652 webpack_require @ app.js:20 (anonymous) @ app.js:49552 webpack_require @ app.js:20 (anonymous) @ app.js:63 (anonymous) @ app.js:66 app.js:2449 TypeError: Cannot read property 'split' of undefined at VueComponent.trans (app.js:115822) at VueComponent.boundFn [as trans] (app.js:924) at VueComponent.parseTranslation (app.js:112485) at Proxy.boundFn (app.js:924) at app.js:112770 at Proxy.renderList (app.js:4404) at app.js:112750 at Proxy.renderList (app.js:4416) at app.js:112655 at Proxy.renderList (app.js:4416) logError @ app.js:2449 globalHandleError @ app.js:2440 handleError @ app.js:2429 Vue._render @ app.js:5208 updateComponent @ app.js:3497 get @ app.js:3847 run @ app.js:3924 flushSchedulerQueue @ app.js:3686 (anonymous) @ app.js:2545 flushCallbacks @ app.js:2466 Promise.then (async) microTimerFunc @ app.js:2514 nextTick @ app.js:2558 queueWatcher @ app.js:3773 update @ app.js:3914 notify @ app.js:1418 reactiveSetter @ app.js:1743 proxySetter @ app.js:4005 (anonymous) @ app.js:112509 Promise.then (async) fetchPermissions @ app.js:112507 boundFn @ app.js:925 mounted @ app.js:112521 callHook @ app.js:3627 insert @ app.js:4822 invokeInsertHook @ app.js:6596 patch @ app.js:6815 Vue._update @ app.js:3369 updateComponent @ app.js:3497 get @ app.js:3847 Watcher @ app.js:3836 mountComponent @ app.js:3504 Vue$3.$mount @ app.js:9161 Vue$3.$mount @ app.js:11522 Vue._init @ app.js:5302 Vue$3 @ app.js:5391 (anonymous) @ app.js:49652 webpack_require @ app.js:20 (anonymous) @ app.js:49552 webpack_require @ app.js:20 (anonymous) @ app.js:63 (anonymous) @ app.js:66

    System Details

    • Operating System - Linux
    • PHP Version - 7.0.32
    • Laravel Version - 5.5.43
    • Asgardcms/Platform version - 3.x
    opened by karneaud 18
  • Fix the bug that prevent user to login or register to the site

    Fix the bug that prevent user to login or register to the site

    This fix is about this issue: https://github.com/AsgardCms/Platform/issues/581

    In short the default route method do not consider the middleware about the localization so the action in the form are incorrect.
    For example for the login the url is just auth/login but the post method responds to en/auth/login so the route is never called.

    With this fix I have added a new helper function called localize_route that get the current url and add the current localization to create the correct url.
    I think that this is a general problem and in the blade views we should use always this function.

    Hope this work for all of you, there is no frontend tests so I can't add tests for this commit, please try and let me know.

    opened by ChristianGiupponi 18
  • "PageExtension" module views/partials no longer appearing in AsgardCMS v3.

    I suspect this is to do with the new way the Page Module uses Vue.js, but without any documentation or guides we are totally stuck!

    @nWidart - Any chance of a quick tutorial or at least pointing us in the right direction please? I know others are wondering how to get this working too.

    Many thanks.

    opened by pavsid 18
  • Upgrade: Bump json5 and laravel-mix in /Themes/Flatly

    Upgrade: Bump json5 and laravel-mix in /Themes/Flatly

    Bumps json5 to 2.2.2 and updates ancestor dependency laravel-mix. These dependencies need to be updated together.

    Updates json5 from 0.5.1 to 2.2.2

    Release notes

    Sourced from json5's releases.

    v2.2.2

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2

    • Fix: Bump minimist to v1.2.5. (#222)

    v2.1.1

    • New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)
    • Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)
    • Fix: Spelling mistakes have been fixed. (#196)

    v2.1.0

    • New: The index.mjs and index.min.mjs browser builds in the dist directory support ES6 modules. (#187)

    v2.0.1

    • Fix: The browser builds in the dist directory support ES5. (#182)

    v2.0.0

    • Major: JSON5 officially supports Node.js v6 and later. Support for Node.js v4 has been dropped. Since Node.js v6 supports ES5 features, the code has been rewritten in native ES5, and the dependence on Babel has been eliminated.

    • New: Support for Unicode 10 has been added.

    • New: The test framework has been migrated from Mocha to Tap.

    • New: The browser build at dist/index.js is no longer minified by default. A minified version is available at dist/index.min.js. (#181)

    • Fix: The warning has been made clearer when line and paragraph separators are used in strings.

    • Fix: package.json5 has been restored, and it is automatically generated and

    ... (truncated)

    Changelog

    Sourced from json5's changelog.

    v2.2.2 [code, diff]

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1 [code, diff]

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0 [code, diff]

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2 [code, diff]

    • Fix: Bump minimist to v1.2.5. (#222)

    v2.1.1 [code, diff]

    • New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)
    • Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)
    • Fix: Spelling mistakes have been fixed. (#196)

    ... (truncated)

    Commits
    • 14f8cb1 2.2.2
    • 10cc7ca docs: update CHANGELOG for v2.2.2
    • 7774c10 fix: add proto to objects and arrays
    • edde30a Readme: slight tweak to intro
    • 97286f8 Improve example in readme
    • d720b4f Improve readme (e.g. explain JSON5 better!) (#291)
    • 910ce25 docs: fix spelling of Aseem
    • 2aab4dd test: require tap as t in cli tests
    • 6d42686 test: remove mocha syntax from tests
    • 4798b9d docs: update installation and usage for modules
    • Additional commits viewable in compare view

    Updates laravel-mix from 0.12.1 to 6.0.49

    Release notes

    Sourced from laravel-mix's releases.

    v6.0.0

    This release brings Laravel Mix current with webpack 5. It additionally includes a variety of bug fixes and enhancements.

    v6.0.0-alpha.0

    Add webpack 5 support.

    v5.0.5

    No release notes provided.

    v5.0.0

    v4.0.7

    • Fixes file path and compile issues on Windows.

    v4.0.0

    To Upgrade...

    npm remove laravel-mix
    npm install [email protected]
    

    After upgrading, if you encounter any vue-template-compiler issues, this is related to the fact that your installed version numbers of vue and vue-template-compiler must be identical. Update one or both to fix this issue.

    New

    • Faster compiles
    • Faster npm installs.
    • Upgraded to webpack 4
    • Upgraded to vue-loader 15
    • Upgraded to Babel 7
    • Automatic vendor extraction. If you call mix.extract() with zero arguments, all vendor dependencies (any package from node_modules/ that you pull in) will automatically be extracted. Nifty!
    • CSS minification (via cssnano) options may be provided 887808f8aea03b5dabc9e7350b66ee01a52e1610
    • PostCSS plugins may be passed to mix.sass/less/stylus() on a per-call basis. This means you may provide unique PostCSS plugins for each mix.sass() call, if desired. 88690a2f770c071dc8160127c42a4f44decf2b56
    • Switched JS optimizing/minification from Uglify to Terser. 5fb180e6e430e99b740a4bce330669cdd8fda29c
    • Switched from node-sass to Dart Sass. While this comes with a small increased compile-time cost, the benefit is faster and more reliable npm installs. 320cecbdb77e222e32903219905d0d8f3754c5ff
    • Improved Babel config merging strategy. You may now override or tweak any default Babel plugins and presets provided through Mix by creating a .babelrc file in your project root. 83f5052eb32c498a90edace47402d66eaf80f4b7

    Bugfixes

    • All npm audit alerts have been fixed, thanks to the upgrade to webpack 4.

    Notes

    • If your project heavily uses JavaScript dynamic imports, you may need to hold off until the release of webpack 5 early next year. There are known compile issues related to this that we cannot fix until then. Once webpack 5 is out, Mix will be updated shortly after. If you're unfamiliar with dynamic imports, then this very likely won't affect your project.
    • Sass support is now an on-demand dependency. In prior versions of Mix, the node-sass and sass-loader dependencies were included out of the box, regardless of whether your project required Sass compilation or not. To help improve install times, these two dependencies will now be installed on-demand if, and only if, your project specifies Sass compilation with mix.sass(). The first time you run npm run dev, the dependencies will be installed and saved to your dev-dependencies list. 5b7a438bcf53bc87ccc08da09b1e816a6088dec8

    ... (truncated)

    Changelog

    Sourced from laravel-mix's changelog.

    Changelog

    6.0.14

    • BabelConfig.fetchBabelRc / static BabelConfig.default / static BabelConfig.generate have all been deprecated. They are no longer used by Mix itself but remain for backwards compatability.
    • MixDefinitionsPlugin.getDefinitions and static MixDefinitionsPlugin.build have been deprecated. They are no longer used by Mix itself but remain for backwards compatability.
    • static Chunks._instance / static Chunks.instance() / static Chunks.reset() are now deprecated and will be removed in a future release.
    • The static methods on HotReloading are now deprecated. They have been replaced with instance methods.
    • The use of the globals Mix, Config, and webpackConfig are now deprecated and will warn on use in Mix v7.

    We are working toward an API for access to Mix for extensions that does not assume that it is a global or that it is the same instance in all cases.

    In the mean time:

    • Uses of Chunks.instance() may be replaced with Mix.chunks
    • Uses of Config may be replaced with Mix.config
    • Uses of webpackConfig may be replaced with Mix.webpackConfig
    • Uses of HotReloading.* methods Mix.hot.*

    6.0

    View upgrade guide.

    Added

    • Support for webpack 5
    • New npx mix executable for triggering your build
    • Support for Vue 3 applications
    • Support for PostCSS 8
    • New mix.vue() and mix.react() commands
    • New mix.alias() command (Learn More)
    • Support for changing the webpack manifest output path (Learn More)
    • New mix.before() hook (Learn More)
    • Improved mix.combine() wildcard support
    • Improved mix.extract() priority and tree-shaking logic

    Changed

    • Fixed "empty CSS file" extraction bug when using dynamic imports
    • Fixed mix.ts() TypeScript bug that skipped Babel transformation in certain cases
    • Fixed and improved PostCSS plugin autoloading and merging
    • Fixed an issue related to hot module reloading when versioning is enabled
    • Added TypeScript types for API
    Upgrade guide

    Sourced from laravel-mix's upgrade guide.

    Upgrade to Mix 6

    npm install laravel-mix@latest
    

    Review Your Dependencies

    Laravel Mix 6 ships with support for the latest versions of numerous dependencies, including webpack 5, PostCSS 8, Vue Loader 16, and more. These are significant releases with their own sets of breaking changes. We've done our best to normalize these changes, but it's still particularly important that you take the time to fully test your build after upgrading to Mix 6.

    Please review your package.json dependencies list for any third-party tools or plugins that may not yet be compatible with webpack 5 or PostCSS 8.

    Check Your Node Version

    Mix has bumped its minimum Node requirement from version 8 to 12.14.0. Please check which version you have installed (node -v) and ensure that it meets this requirement.

    Update Your NPM Scripts

    If your build throws an error such as Unknown argument: --hide-modules, the scripts section of your package.json file will need to be updated. The Webpack 5 CLI removed a number of options that your NPM scripts was likely referencing.

    While you're at it, go ahead and switch over to the new Mix CLI.

    Before
    "scripts": {
        "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch": "npm run development -- --watch",
        "watch-poll": "npm run watch -- --watch-poll",
        "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --disable-host-check --config=node_modules/laravel-mix/setup/webpack.config.js",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
    }
    </tr></table> 
    

    ... (truncated)

    Commits
    Maintainer changes

    This version was pushed to npm by thecrypticace, a new releaser for laravel-mix since your current version.


    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Upgrade: Bump json5, less-loader and laravel-mix in /Themes/Adminlte

    Upgrade: Bump json5, less-loader and laravel-mix in /Themes/Adminlte

    Bumps json5 to 2.2.2 and updates ancestor dependencies json5, less-loader and laravel-mix. These dependencies need to be updated together.

    Updates json5 from 0.5.1 to 2.2.2

    Release notes

    Sourced from json5's releases.

    v2.2.2

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2

    • Fix: Bump minimist to v1.2.5. (#222)

    v2.1.1

    • New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)
    • Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)
    • Fix: Spelling mistakes have been fixed. (#196)

    v2.1.0

    • New: The index.mjs and index.min.mjs browser builds in the dist directory support ES6 modules. (#187)

    v2.0.1

    • Fix: The browser builds in the dist directory support ES5. (#182)

    v2.0.0

    • Major: JSON5 officially supports Node.js v6 and later. Support for Node.js v4 has been dropped. Since Node.js v6 supports ES5 features, the code has been rewritten in native ES5, and the dependence on Babel has been eliminated.

    • New: Support for Unicode 10 has been added.

    • New: The test framework has been migrated from Mocha to Tap.

    • New: The browser build at dist/index.js is no longer minified by default. A minified version is available at dist/index.min.js. (#181)

    • Fix: The warning has been made clearer when line and paragraph separators are used in strings.

    • Fix: package.json5 has been restored, and it is automatically generated and

    ... (truncated)

    Changelog

    Sourced from json5's changelog.

    v2.2.2 [code, diff]

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1 [code, diff]

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

    v2.2.0 [code, diff]

    • New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

    v2.1.3 [code, diff]

    • Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

    v2.1.2 [code, diff]

    • Fix: Bump minimist to v1.2.5. (#222)

    v2.1.1 [code, diff]

    • New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)
    • Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)
    • Fix: Spelling mistakes have been fixed. (#196)

    ... (truncated)

    Commits
    • 14f8cb1 2.2.2
    • 10cc7ca docs: update CHANGELOG for v2.2.2
    • 7774c10 fix: add proto to objects and arrays
    • edde30a Readme: slight tweak to intro
    • 97286f8 Improve example in readme
    • d720b4f Improve readme (e.g. explain JSON5 better!) (#291)
    • 910ce25 docs: fix spelling of Aseem
    • 2aab4dd test: require tap as t in cli tests
    • 6d42686 test: remove mocha syntax from tests
    • 4798b9d docs: update installation and usage for modules
    • Additional commits viewable in compare view

    Updates less-loader from 4.0.5 to 11.1.0

    Release notes

    Sourced from less-loader's releases.

    v11.1.0

    11.1.0 (2022-10-06)

    Features

    v11.0.0

    11.0.0 (2022-05-17)

    ⚠ BREAKING CHANGES

    • minimum supported Node.js version is 14.15.0

    v10.2.0

    10.2.0 (2021-10-18)

    Features

    v10.1.0

    10.1.0 (2021-10-11)

    Features

    Bug Fixes

    • only call addDependency on absolute paths (fa11ce7)

    v10.0.1

    10.0.1 (2021-07-02)

    Bug Fixes

    v10.0.0

    10.0.0 (2021-06-17)

    ⚠ BREAKING CHANGES

    ... (truncated)

    Changelog

    Sourced from less-loader's changelog.

    11.1.0 (2022-10-06)

    Features

    11.0.0 (2022-05-17)

    ⚠ BREAKING CHANGES

    • minimum supported Node.js version is 14.15.0

    10.2.0 (2021-10-18)

    Features

    10.1.0 (2021-10-11)

    Features

    Bug Fixes

    • only call addDependency on absolute paths (fa11ce7)

    10.0.1 (2021-07-02)

    Bug Fixes

    10.0.0 (2021-06-17)

    ⚠ BREAKING CHANGES

    • less.webpackLoaderContext was removed, please use pluginManager.webpackLoaderContext

    Bug Fixes

    ... (truncated)

    Commits
    • 21caa3e chore(release): 11.1.0
    • 43cd20c feat: allow to extend conditionNames (#488)
    • c1aa4f5 chore: update dependencies to the latest version (#487)
    • 2dcfe42 chore: update commitlint action (#486)
    • 60d6a29 chore: run cancel workflow on pull request (#485)
    • 4e81ee0 chore: update jest to the latest version (#483)
    • 965f5d8 ci: update github workflow security permissions (#482)
    • 454e187 chore: upgrade dependencies to the latest version (#481)
    • bb799d1 ci: add job to cancel previous runs (#480)
    • d292548 chore: update dependencies to the latest version (#479)
    • Additional commits viewable in compare view
    Maintainer changes

    This version was pushed to npm by evilebottnawi, a new releaser for less-loader since your current version.


    Updates laravel-mix from 1.5.0 to 6.0.49

    Release notes

    Sourced from laravel-mix's releases.

    v6.0.0

    This release brings Laravel Mix current with webpack 5. It additionally includes a variety of bug fixes and enhancements.

    v6.0.0-alpha.0

    Add webpack 5 support.

    v5.0.5

    No release notes provided.

    v5.0.0

    v4.0.7

    • Fixes file path and compile issues on Windows.

    v4.0.0

    To Upgrade...

    npm remove laravel-mix
    npm install [email protected]
    

    After upgrading, if you encounter any vue-template-compiler issues, this is related to the fact that your installed version numbers of vue and vue-template-compiler must be identical. Update one or both to fix this issue.

    New

    • Faster compiles
    • Faster npm installs.
    • Upgraded to webpack 4
    • Upgraded to vue-loader 15
    • Upgraded to Babel 7
    • Automatic vendor extraction. If you call mix.extract() with zero arguments, all vendor dependencies (any package from node_modules/ that you pull in) will automatically be extracted. Nifty!
    • CSS minification (via cssnano) options may be provided 887808f8aea03b5dabc9e7350b66ee01a52e1610
    • PostCSS plugins may be passed to mix.sass/less/stylus() on a per-call basis. This means you may provide unique PostCSS plugins for each mix.sass() call, if desired. 88690a2f770c071dc8160127c42a4f44decf2b56
    • Switched JS optimizing/minification from Uglify to Terser. 5fb180e6e430e99b740a4bce330669cdd8fda29c
    • Switched from node-sass to Dart Sass. While this comes with a small increased compile-time cost, the benefit is faster and more reliable npm installs. 320cecbdb77e222e32903219905d0d8f3754c5ff
    • Improved Babel config merging strategy. You may now override or tweak any default Babel plugins and presets provided through Mix by creating a .babelrc file in your project root. 83f5052eb32c498a90edace47402d66eaf80f4b7

    Bugfixes

    • All npm audit alerts have been fixed, thanks to the upgrade to webpack 4.

    Notes

    • If your project heavily uses JavaScript dynamic imports, you may need to hold off until the release of webpack 5 early next year. There are known compile issues related to this that we cannot fix until then. Once webpack 5 is out, Mix will be updated shortly after. If you're unfamiliar with dynamic imports, then this very likely won't affect your project.
    • Sass support is now an on-demand dependency. In prior versions of Mix, the node-sass and sass-loader dependencies were included out of the box, regardless of whether your project required Sass compilation or not. To help improve install times, these two dependencies will now be installed on-demand if, and only if, your project specifies Sass compilation with mix.sass(). The first time you run npm run dev, the dependencies will be installed and saved to your dev-dependencies list. 5b7a438bcf53bc87ccc08da09b1e816a6088dec8

    ... (truncated)

    Changelog

    Sourced from laravel-mix's changelog.

    Changelog

    6.0.14

    • BabelConfig.fetchBabelRc / static BabelConfig.default / static BabelConfig.generate have all been deprecated. They are no longer used by Mix itself but remain for backwards compatability.
    • MixDefinitionsPlugin.getDefinitions and static MixDefinitionsPlugin.build have been deprecated. They are no longer used by Mix itself but remain for backwards compatability.
    • static Chunks._instance / static Chunks.instance() / static Chunks.reset() are now deprecated and will be removed in a future release.
    • The static methods on HotReloading are now deprecated. They have been replaced with instance methods.
    • The use of the globals Mix, Config, and webpackConfig are now deprecated and will warn on use in Mix v7.

    We are working toward an API for access to Mix for extensions that does not assume that it is a global or that it is the same instance in all cases.

    In the mean time:

    • Uses of Chunks.instance() may be replaced with Mix.chunks
    • Uses of Config may be replaced with Mix.config
    • Uses of webpackConfig may be replaced with Mix.webpackConfig
    • Uses of HotReloading.* methods Mix.hot.*

    6.0

    View upgrade guide.

    Added

    • Support for webpack 5
    • New npx mix executable for triggering your build
    • Support for Vue 3 applications
    • Support for PostCSS 8
    • New mix.vue() and mix.react() commands
    • New mix.alias() command (Learn More)
    • Support for changing the webpack manifest output path (Learn More)
    • New mix.before() hook (Learn More)
    • Improved mix.combine() wildcard support
    • Improved mix.extract() priority and tree-shaking logic

    Changed

    • Fixed "empty CSS file" extraction bug when using dynamic imports
    • Fixed mix.ts() TypeScript bug that skipped Babel transformation in certain cases
    • Fixed and improved PostCSS plugin autoloading and merging
    • Fixed an issue related to hot module reloading when versioning is enabled
    • Added TypeScript types for API
    Upgrade guide

    Sourced from laravel-mix's upgrade guide.

    Upgrade to Mix 6

    npm install laravel-mix@latest
    

    Review Your Dependencies

    Laravel Mix 6 ships with support for the latest versions of numerous dependencies, including webpack 5, PostCSS 8, Vue Loader 16, and more. These are significant releases with their own sets of breaking changes. We've done our best to normalize these changes, but it's still particularly important that you take the time to fully test your build after upgrading to Mix 6.

    Please review your package.json dependencies list for any third-party tools or plugins that may not yet be compatible with webpack 5 or PostCSS 8.

    Check Your Node Version

    Mix has bumped its minimum Node requirement from version 8 to 12.14.0. Please check which version you have installed (node -v) and ensure that it meets this requirement.

    Update Your NPM Scripts

    If your build throws an error such as Unknown argument: --hide-modules, the scripts section of your package.json file will need to be updated. The Webpack 5 CLI removed a number of options that your NPM scripts was likely referencing.

    While you're at it, go ahead and switch over to the new Mix CLI.

    Before
    "scripts": {
        "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch": "npm run development -- --watch",
        "watch-poll": "npm run watch -- --watch-poll",
        "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --disable-host-check --config=node_modules/laravel-mix/setup/webpack.config.js",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
    }
    </tr></table> 
    

    ... (truncated)

    Commits
    Maintainer changes

    This version was pushed to npm by thecrypticace, a new releaser for laravel-mix since your current version.


    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Upgrade: Bump express and browser-sync in /Themes/Flatly

    Upgrade: Bump express and browser-sync in /Themes/Flatly

    Bumps express and browser-sync. These dependencies needed to be updated together. Updates express from 4.15.3 to 4.18.2

    Release notes

    Sourced from express's releases.

    4.18.2

    4.18.1

    • Fix hanging on large stack of sync routes

    4.18.0

    ... (truncated)

    Changelog

    Sourced from express's changelog.

    4.18.2 / 2022-10-08

    4.18.1 / 2022-04-29

    • Fix hanging on large stack of sync routes

    4.18.0 / 2022-04-25

    ... (truncated)

    Commits

    Updates browser-sync from 2.18.12 to 2.27.10

    Release notes

    Sourced from browser-sync's releases.

    2.27.9

    What's Changed

    A bug prevented the help output from displaying - it was introduced when the CLI parser yargs was updated, and is now fixed :)

    Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.27.8...v2.27.9

    2.27.8

    This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)

    PR:

    Resolved Issues:

    Thanks to @​lachieh for the original PR, which helped me land this fix

    added snippet: boolean option

    This release adds a feature to address BrowserSync/browser-sync#1882

    Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new snippet option :)

    browser-sync . --no-snippet
    

    or in any Browsersync configuration

    const config = {
      snippet: false,
    };
    

    the original request was related to Eleventy usage, so here's how that would look

    eleventyConfig.setBrowserSyncConfig({
      snippet: false,
    });
    

    ... (truncated)

    Changelog

    Sourced from browser-sync's changelog.

    2.23.1 (2018-01-01)

    2.8.2 (2015-07-31)

    Bug Fixes

    • https: add newly generated ssl self-signed certs that will expire for 10 years - fixes (45104a7), closes #750

    2.8.1 (2015-07-28)

    Bug Fixes

    • web-sockets: Use separate server for web sockets in proxy mode - fixes #625 (40017b4), closes #625

    Features

    • serve-static: Added option serveStatic to allow proxy/snippet mode to easily serve local fil (384ef67)

    2.7.13 (2015-06-28)

    Bug Fixes

    • snippet: Allow async attribute to be removed from snippet with snippetOptions.async = fal (c32bec6), closes #670
    • socket-options: allow socket.domain string|fn for setting domain only on socket path - fixes #69 (5157432), closes #690

    Features

    • api: expose sockets to public api (985682c)

    2.7.12 (2015-06-17)

    Bug Fixes

    • client-script: allow proxy to also use client script middleware (c5fdbbf)
    • client-script: serve cached/gzipped client JS file - fixes #657 (dbe9ffe), closes #657

    ... (truncated)

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Upgrade: Bump engine.io and browser-sync in /Themes/Flatly

    Upgrade: Bump engine.io and browser-sync in /Themes/Flatly

    Bumps engine.io and browser-sync. These dependencies needed to be updated together. Updates engine.io from 1.8.0 to 6.2.1

    Release notes

    Sourced from engine.io's releases.

    6.2.1

    :warning: This release contains an important security fix :warning:

    A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

    Error: read ECONNRESET
        at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (internal/streams/destroy.js:106:8)
        at emitErrorCloseNT (internal/streams/destroy.js:74:3)
        at processTicksAndRejections (internal/process/task_queues.js:80:21) {
      errno: -104,
      code: 'ECONNRESET',
      syscall: 'read'
    }
    

    Please upgrade as soon as possible.

    Bug Fixes

    • catch errors when destroying invalid upgrades (#658) (425e833)

    6.2.0

    Features

    • add the "maxPayload" field in the handshake details (088dcb4)

    So that clients in HTTP long-polling can decide how many packets they have to send to stay under the maxHttpBufferSize value.

    This is a backward compatible change which should not mandate a new major revision of the protocol (we stay in v4), as we only add a field in the JSON-encoded handshake data:

    0{"sid":"lv_VI97HAXpY6yYWAAAC","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000,"maxPayload":1000000}
    

    Links

    6.1.3

    Bug Fixes

    • typings: allow CorsOptionsDelegate as cors options (#641) (a463d26)
    • uws: properly handle chunked content (#642) (3367440)

    ... (truncated)

    Changelog

    Sourced from engine.io's changelog.

    6.2.1 (2022-11-20)

    :warning: This release contains an important security fix :warning:

    A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

    Error: read ECONNRESET
        at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (internal/streams/destroy.js:106:8)
        at emitErrorCloseNT (internal/streams/destroy.js:74:3)
        at processTicksAndRejections (internal/process/task_queues.js:80:21) {
      errno: -104,
      code: 'ECONNRESET',
      syscall: 'read'
    }
    

    Please upgrade as soon as possible.

    Bug Fixes

    • catch errors when destroying invalid upgrades (#658) (425e833)

    3.6.0 (2022-06-06)

    Bug Fixes

    Features

    • decrease the default value of maxHttpBufferSize (58e274c)

    This change reduces the default value from 100 mb to a more sane 1 mb.

    This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data.

    See also: https://github.com/advisories/GHSA-j4f2-536g-r55m

    • increase the default value of pingTimeout (f55a79a)

    ... (truncated)

    Commits
    • 24b847b chore(release): 6.2.1
    • 425e833 fix: catch errors when destroying invalid upgrades (#658)
    • 99adb00 chore(deps): bump xmlhttprequest-ssl and engine.io-client in /examples/latenc...
    • d196f6a chore(deps): bump minimatch from 3.0.4 to 3.1.2 (#660)
    • 7c1270f chore(deps): bump nanoid from 3.1.25 to 3.3.1 (#659)
    • 535a01d ci: add Node.js 18 in the test matrix
    • 1b71a6f docs: remove "Vanilla JS" highlight from README (#656)
    • 917d1d2 refactor: replace deprecated String.prototype.substr() (#646)
    • 020801a chore: add changelog for version 3.6.0
    • ed1d6f9 test: make test script work on Windows (#643)
    • Additional commits viewable in compare view

    Updates browser-sync from 2.18.12 to 2.27.10

    Release notes

    Sourced from browser-sync's releases.

    2.27.9

    What's Changed

    A bug prevented the help output from displaying - it was introduced when the CLI parser yargs was updated, and is now fixed :)

    Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.27.8...v2.27.9

    2.27.8

    This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)

    PR:

    Resolved Issues:

    Thanks to @​lachieh for the original PR, which helped me land this fix

    added snippet: boolean option

    This release adds a feature to address BrowserSync/browser-sync#1882

    Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new snippet option :)

    browser-sync . --no-snippet
    

    or in any Browsersync configuration

    const config = {
      snippet: false,
    };
    

    the original request was related to Eleventy usage, so here's how that would look

    eleventyConfig.setBrowserSyncConfig({
      snippet: false,
    });
    

    ... (truncated)

    Changelog

    Sourced from browser-sync's changelog.

    2.23.1 (2018-01-01)

    2.8.2 (2015-07-31)

    Bug Fixes

    • https: add newly generated ssl self-signed certs that will expire for 10 years - fixes (45104a7), closes #750

    2.8.1 (2015-07-28)

    Bug Fixes

    • web-sockets: Use separate server for web sockets in proxy mode - fixes #625 (40017b4), closes #625

    Features

    • serve-static: Added option serveStatic to allow proxy/snippet mode to easily serve local fil (384ef67)

    2.7.13 (2015-06-28)

    Bug Fixes

    • snippet: Allow async attribute to be removed from snippet with snippetOptions.async = fal (c32bec6), closes #670
    • socket-options: allow socket.domain string|fn for setting domain only on socket path - fixes #69 (5157432), closes #690

    Features

    • api: expose sockets to public api (985682c)

    2.7.12 (2015-06-17)

    Bug Fixes

    • client-script: allow proxy to also use client script middleware (c5fdbbf)
    • client-script: serve cached/gzipped client JS file - fixes #657 (dbe9ffe), closes #657

    ... (truncated)

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Entity generation not working correctly

    Entity generation not working correctly

    Summary of issue

    Using the command: php artisan asgard:entity:scaffold generates an entity but stops abruptly at the middle. I tried the command but it doesn't seem to work. The entity class and interface in the Repositories directory are created, but it doesn't go further than that.

    image

    I tried checking the folder permissions, plus clearing the cache and config. None of it seemed to work. I manually created the Cache/CacheCrDecorator but then I got this error:

    image

    Steps to reproduce

    System Details

    Windows - Operating System 7.4 - PHP Version 5.5 - Laravel Version 3.0 - Asgardcms/Platform version

    opened by preet-adhikari 0
  • Upgrade: Bump socket.io-parser and browser-sync in /Themes/Flatly

    Upgrade: Bump socket.io-parser and browser-sync in /Themes/Flatly

    Bumps socket.io-parser and browser-sync. These dependencies needed to be updated together. Updates socket.io-parser from 2.3.1 to 4.2.1

    Release notes

    Sourced from socket.io-parser's releases.

    4.2.1

    Bug Fixes

    • check the format of the index of each attachment (b5d0cb7)

    Links

    4.2.0

    Features

    • allow the usage of custom replacer and reviver (#112) (b08bc1a)

    Links

    4.1.2

    Bug Fixes

    • allow objects with a null prototype in binary packets (#114) (7f6b262)

    Links

    4.1.1

    Links

    4.1.0

    Features

    • provide an ESM build with and without debug (388c616)

    Links

    4.0.5

    Bug Fixes

    • check the format of the index of each attachment (b559f05)

    Links

    ... (truncated)

    Changelog

    Sourced from socket.io-parser's changelog.

    4.2.1 (2022-06-27)

    Bug Fixes

    • check the format of the index of each attachment (b5d0cb7)

    4.2.0 (2022-04-17)

    Features

    • allow the usage of custom replacer and reviver (#112) (b08bc1a)

    4.1.2 (2022-02-17)

    Bug Fixes

    • allow objects with a null prototype in binary packets (#114) (7f6b262)

    4.1.1 (2021-10-14)

    4.1.0 (2021-10-11)

    Features

    • provide an ESM build with and without debug (388c616)

    4.0.4 (2021-01-15)

    Bug Fixes

    • allow integers as event names (1c220dd)

    4.0.3 (2021-01-05)

    4.0.2 (2020-11-25)

    ... (truncated)

    Commits
    • 5a2ccff chore(release): 4.2.1
    • b5d0cb7 fix: check the format of the index of each attachment
    • c7514b5 chore(release): 4.2.0
    • 931f152 chore: add Node.js 16 in the test matrix
    • 6c9cb27 chore: bump @​socket.io/component-emitter to version 3.1.0
    • b08bc1a feat: allow the usage of custom replacer and reviver (#112)
    • aed252c chore(release): 4.1.2
    • 89209fa chore: bump cached-path-relative from 1.0.2 to 1.1.0 (#113)
    • 0a3b556 chore: bump path-parse from 1.0.6 to 1.0.7 (#108)
    • 7f6b262 fix: allow objects with a null prototype in binary packets (#114)
    • Additional commits viewable in compare view

    Updates browser-sync from 2.18.12 to 2.27.10

    Release notes

    Sourced from browser-sync's releases.

    2.27.9

    What's Changed

    A bug prevented the help output from displaying - it was introduced when the CLI parser yargs was updated, and is now fixed :)

    Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.27.8...v2.27.9

    2.27.8

    This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)

    PR:

    Resolved Issues:

    Thanks to @​lachieh for the original PR, which helped me land this fix

    added snippet: boolean option

    This release adds a feature to address BrowserSync/browser-sync#1882

    Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new snippet option :)

    browser-sync . --no-snippet
    

    or in any Browsersync configuration

    const config = {
      snippet: false,
    };
    

    the original request was related to Eleventy usage, so here's how that would look

    eleventyConfig.setBrowserSyncConfig({
      snippet: false,
    });
    

    ... (truncated)

    Changelog

    Sourced from browser-sync's changelog.

    2.23.1 (2018-01-01)

    2.8.2 (2015-07-31)

    Bug Fixes

    • https: add newly generated ssl self-signed certs that will expire for 10 years - fixes (45104a7), closes #750

    2.8.1 (2015-07-28)

    Bug Fixes

    • web-sockets: Use separate server for web sockets in proxy mode - fixes #625 (40017b4), closes #625

    Features

    • serve-static: Added option serveStatic to allow proxy/snippet mode to easily serve local fil (384ef67)

    2.7.13 (2015-06-28)

    Bug Fixes

    • snippet: Allow async attribute to be removed from snippet with snippetOptions.async = fal (c32bec6), closes #670
    • socket-options: allow socket.domain string|fn for setting domain only on socket path - fixes #69 (5157432), closes #690

    Features

    • api: expose sockets to public api (985682c)

    2.7.12 (2015-06-17)

    Bug Fixes

    • client-script: allow proxy to also use client script middleware (c5fdbbf)
    • client-script: serve cached/gzipped client JS file - fixes #657 (dbe9ffe), closes #657

    ... (truncated)

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
Releases(3.6.1)
Multilingual CMS built with Laravel.

TypiCMS TypiCMS is a modular multilingual content management system built with Laravel. Out of the box you can manage pages, events, news, places, men

TypiCMS, Laravel multilingual CMS 1.1k Jan 7, 2023
Multilingual CMS built with Laravel.

TypiCMS TypiCMS is a modular multilingual content management system built with Laravel. Out of the box you can manage pages, events, news, places, men

TypiCMS, Laravel multilingual CMS 973 Jun 25, 2021
Modular CMS powered by CakePHP

QuickAppsCMS Free open source content management system for PHP, released under GPL License and powered by CakePHP 3.0 MVC framework. This is an unsta

QuickApps 162 Dec 18, 2022
Polymorphic and Multilingual CMS powered by Laravel

Nuclear CMS Polymorphic and multilingual content management system. Nuclear is a polymorphic and multilingual content management system powered by Lar

Nuclear CMS 36 Nov 29, 2022
A multilingual, extensible, community oriented CMS developed in PHP

ImpressCMS is a community developed Content Management System. With this tool maintaining the content of a website becomes as easy as writing a word d

ImpressCMS 26 Dec 14, 2022
A Concrete CMS package to add interfaces to translate multilingual content. You can translate content manually, or use cloud API.

Concrete CMS add-on: Macareux Content Translator Concrete CMS has powerful features to manage multilingual content by its default. You can add languag

株式会社マカルーデジタル 3 Nov 28, 2022
A multilingual, extensible, community oriented CMS developed in PHP

ImpressCMS is a community developed Content Management System. With this tool maintaining the content of a website becomes as easy as writing a word d

ImpressCMS 26 Dec 14, 2022
The modular open source laravel administration panel

Laralum What is Laralum? Laralum is an idea that came to our mind when we found no CMS that had the right balance between power and flexibility. This

Laralum 297 Nov 10, 2022
Simple, modular content management system adapted for launch pages and one-page websites

Segmint Segmint is an easy-to-use flat-file landing page framework, allowing quick and efficient prototyping and deployment - perfect for freelancers

null 2 Jul 19, 2022
Amila Laravel CMS - Free, open-source Simple Bootstrap Laravel CMS

Simple Bootstrap Laravel CMS. Support Laravel 8.x Can integrate into any existing Laravel project. Only add few database tables with prefixes, not affect your existing database tables. Support Laravel 7.x & Laravel 6.x & Laravel 5.x & MySql & PostgreSql - Amila Laravel CMS

Alex Zeng 96 Sep 6, 2022
Doptor CMS is a Laravel 5 based CMS

Introduction Doptor CMS is a Laravel 5 based CMS. Find out more about Doptor by reading below. ;) About Doptor CMS Doptor is an Integrated and well-de

DOPTOR 4 Sep 11, 2022
Bootstrap CMS - PHP CMS powered by Laravel 5 and Sentry

Bootstrap CMS Bootstrap CMS was created by, and is maintained by Graham Campbell, and is a PHP CMS powered by Laravel 5.1 and Sentry. It utilises many

Bootstrap CMS 2.5k Dec 27, 2022
KodiCMS - CMS built on Laravel 5.2

KodiCMS based on Laravel PHP Framework English Version Установка (Installation): Клонировать репозиторий (Clone repository) git clone https://github.c

KodiCMS built on Laravel 163 Nov 27, 2022
ARCANESOFT - CMS built with Laravel Framework.

ARCANESOFT CMS built with Laravel Framework. By ARCANEDEV© Available Packages Production Package Description arcanedev/breadcrumbs A simple & easy way

ARCANESOFT 11 Oct 10, 2020
A PHP 5.3 CMS built on top of Laravel 4 and other composer components.

Anvil Forge your website! A PHP 5.3 CMS built on top of Laravel 4 and other composer components. Installation Installing Anvil is easy. Run the follow

Loïc Sharma 17 May 3, 2022
Flextype is an open-source Hybrid Content Management System with the freedom of a headless CMS and with the full functionality of a traditional CMS

Flextype is an open-source Hybrid Content Management System with the freedom of a headless CMS and with the full functionality of a traditional CMS. Building this Content Management System, we focused on simplicity. To achieve this, we implemented a simple but powerful API's.

Flextype 524 Dec 30, 2022
PHPVibe Open source video CMS / Video Sharing CMS / Youtube Api v3 / Video Embeds

PHPVibe Video CMS Free Video Sharing CMS The modern choice of design inspired by Youtube and a social videos sharing module that may just cut it for y

MediaVibe 71 Dec 18, 2022
NukeViet 132 Nov 27, 2022
BaiCloud-cms is a powerful open source CMS that allows you to create professional websites and scalable web applications. Visit the project website for more information.

BaiCloud-cms About BaiCloud-cms is a powerful open source CMS that allows you to create professional websites and scalable web applications. Visit the

null 5 Aug 15, 2022