laravel-frontend-presets / bulma Goto Github PK

Command:
composer require laravel-frontend-presets/bulma

Issue:

Problem 1
- laravel-frontend-presets/bulma v3.0.4 requires laravel/framework ^7.0 -> satisfiable by laravel/framework[7.x-dev, v7.0.0, v7.0.1, v7.0.2, v7.0.3, v7.0.4, v7.0.5, v7.0.6, v7.0.7, v7.0.8, v7.1.0, v7.1.1, v7.1.2, v7.1.3, v7.10.0, v7.10.1, v7.10.2, v7.10.3, v7.11.0, v7.12.0, v7.13.0, v7.14.0, v7.14.1, v7.15.0, v7.16.0, v7.16.1, v7.17.0, v7.17.1, v7.17.2, v7.18.0, v7.19.0, v7.19.1, v7.2.0, v7.2.1, v7.2.2, v7.20.0, v7.21.0, v7.22.0, v7.22.1, v7.22.2, v7.22.3, v7.22.4, v7.23.0, v7.23.1, v7.23.2, v7.24.0, v7.25.0, v7.26.0, v7.26.1, v7.27.0, v7.28.0, v7.28.1, v7.28.2, v7.28.3, v7.28.4, v7.29.0, v7.29.1, v7.29.2, v7.29.3, v7.3.0, v7.30.0, v7.30.1, v7.30.2, v7.30.3, v7.30.4, v7.4.0, v7.5.0, v7.5.1, v7.5.2, v7.6.0, v7.6.1, v7.6.2, v7.7.0, v7.7.1, v7.8.0, v7.8.1, v7.9.0, v7.9.1, v7.9.2] but these conflict with your requirements or minimum-stability.

I have a proyect in laravel 5.4, is posible install the preset for this version?

Trying to add this to a new Laravel 7 Project, receiving errors when attempting install, do you have something in the works to support L7? Looks like a simple update in your composer.json file to include "^7.0" would suffice, unless you have internal changes as well.

❯ composer require laravel-frontend-presets/bulma
Using version ^3.0 for laravel-frontend-presets/bulma
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for laravel/framework (locked at v7.6.1, required as ^7.0) -> satisfiable by laravel/framework[v7.6.1].
    - laravel-frontend-presets/bulma v3.0.0 requires laravel/framework ^6.0 -> satisfiable by laravel/framework[6.x-dev].
    - laravel-frontend-presets/bulma v3.0.1 requires laravel/framework ^6.0 -> satisfiable by laravel/framework[6.x-dev].
    - laravel-frontend-presets/bulma v3.0.2 requires laravel/framework ^6.0 -> satisfiable by laravel/framework[6.x-dev].
    - Conclusion: don't install laravel/framework 6.x-dev
    - Installation request for laravel-frontend-presets/bulma ^3.0 -> satisfiable by laravel-frontend-presets/bulma[v3.0.0, v3.0.1, v3.0.2].


Installation failed, reverting ./composer.json to its original content.

Tried to install on fresh laravel 7.9.2.

mark@Linux-Mint:/laravel/bulma$ php artisan --version
Laravel Framework 7.9.2
mark@Linux-Mint:/laravel/bulma$ composer require laravel-frontend-presets/bulma
Using version ^3.0 for laravel-frontend-presets/bulma
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 1 install, 0 updates, 0 removals

• Installing laravel-frontend-presets/bulma (v3.0.3): Loading from cache
  Writing lock file
  Generating optimized autoload files

Illuminate\Foundation\ComposerScripts::postAutoloadDump
@php artisan package:discover --ansi

Error

Class 'Illuminate\Foundation\Console\PresetCommand' not found

at vendor/laravel-frontend-presets/bulma/src/BulmaPresetServiceProvider.php:16
12| * @return void
13| */
14| public function boot()
15| {

16| PresetCommand::macro('bulma', function ($command) {
17| BulmaPreset::install(false);
18| $command->info('Bulma scaffolding installed successfully.');
19| $command->comment('Please run "npm install && npm run dev" to compile your fresh scaffolding.');
20| });

  +8 vendor frames 

9 [internal]:0
Illuminate\Foundation\Application::Illuminate\Foundation{closure}(Object(LaravelFrontendPresets\BulmaPreset\BulmaPresetServiceProvider))

  +5 vendor frames 

15 artisan:37
Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

Installation failed, reverting ./composer.json to its original content.

Thanks.

I've just installed this preset, and when i ran npm install command, it gave me an error saying "No matching version found for bulma-extensions@^0.5.3".

I then ran npm show bulma-extensions versions, and version numbers went up to 0.5.2.

Digging a little bit more: on bulma-extensions github repo only the 0.5.2 release appears. On npm it says the latest of 21 releases is 0.5.2... BUT on bulma-extensions documentation site, it shows the latest version as 0.5.3

Running npm run dev, I had this error:

ERROR in ./resources/sass/app.scss
Module build failed (from ./node_modules/css-loader/index.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
SassError: semicolons aren't allowed in the indented syntax.
   ╷
86 │                 vertical-align: middle;
   │                                       ^
   ╵
  node_modules/bulma-extensions/bulma-slider/src/sass/index.sass 86:27  @import
  resources/sass/bulma-extensions.sass 16:9                             @import
  resources/sass/bulma.sass 20:9                                        @import

So there was a semicolon on line 86 and also one on line 91 of node_modules/bulma-extensions/bulma-slider/src/sass/index.sass

After removing the semicolons, I had no errors.

The variable target doesn't seem to exist, or maybe I am wrong

The styles doesn't apply for inputs, I didn't modify any of login.blade.php

I notice also that I have an old version of Bulma but I don't know it is normal.

I followed this tutorial https://github.com/laravel-frontend-presets/bulma#usage, it doens't work

There is a stray semicolon at line 210 of file "node_modules/bulma-extensions/bulma-calendar/dist/css/bulma-calendar.sass"

Removing it, causes the error to disappear

The package specifically requires only v5.5 and doesn't yet support v5.6.
Could the requirement be loosen to test v5.6 compatibility with ^5.5.* as I can't see a reason for it not working.

If you look at the documentation for these two specific controls, they require specific js files to function:

The extension comes with a JavaScript implementation to expand / collapse accordion items. Don't forget to include it in your project.

<script type="text/javascript" src="/node_modules/bulma-extensions/bulma-accordion/dist/bulma-accordion.min.js"></script>

And

The extension comes with a JavaScript implementation to manage input tags type. Don't forget to include it in your project.

<script type="text/javascript" src="/node_modules/bulma-extensions/bulma-tagsinput/dist/bulma-tagsinput.min.js"></script>

And I do see you have included them in bulma-extension.js:
require('bulma-extensions/bulma-accordion/dist/bulma-accordion');
[...]
require('bulma-extensions/bulma-tagsinput/dist/bulma-tagsinput');

I manually copied the javascript file /node_modules/bulma-extensions/bulma-tagsinput/dist/bulma-tagsinput.min.js over using mix.js and referenced it directly in <script> and the control worked fine. But following your instructions on the default setup, these 2 specifically don't seem to work.

Hi,
node_modules/bulma-extensions/bulma-slider/src/sass/index.sass 86:27
@import - Semicolons aren't allowed in the indented syntax.

When I compile assets with npm run dev I get this error:

Laravel Mix

Error: ./bootstrap
Can't resolve 'bootstrap-sass' in /var/www//resources/assets/js

To fix this you need to comment out line 13 in resources/assets/js/bootstrap.js

10 try {
11    window.$ = window.jQuery = require('jquery');
12 
13    // require('bootstrap-sass');
14 } catch (e) {}

there's an issue with imports for iconPicker extension from Bulma Extensions. extension name is in camelCase, while in repo it's all lowercase

current code:
resources/assets/js/bulma-extensions.js
require('bulma-extensions/bulma-iconpicker/dist/bulma-iconPicker');
resources/assets/sass/bulma-extensions.sass
@import "node_modules/bulma-extensions/bulma-iconpicker/dist/bulma-iconPicker.sass"

correct code:
resources/assets/js/bulma-extensions.js
require('bulma-extensions/bulma-iconpicker/dist/bulma-iconpicker');
resources/assets/sass/bulma-extensions.sass
@import "node_modules/bulma-extensions/bulma-iconpicker/dist/bulma-iconpicker.sass"

proof & source:
https://github.com/Wikiki/bulma-iconpicker/tree/a695d934b491f03876b306aa00e663f8716b8644

When using Laravel 6.5+ and the latest bulma-extension here then the login page looks broken visually. And during compilation it says it can't find some bootstrap stuff but i thought it was all replaced by bulma now?

And when is an update to Bulma 0.8 coming?

As of laravel 5.7, running the bulma preset will not work because resources folder has changed and all of folders inside assets folder has moved up, and asset has been removed.
Change it pkease to the correct folder and it should work great. Thanks.

Could we have a Usage paragraph for non-fresh install of Laravel 5.5 ?

Versions

• Vagrant: v2.2.2
• Provider: Virtualbox v6.0.0 r127566 (Qt5.6.2)
• Homestead: v2.2.2
• Nodejs: v11.6.0
• npm: v6.5.0

Host operating system

Windows 10 1809

Homestead.yaml

# ---
ip: "192.168.10.10"
memory: 10240
cpus: 4
provider: virtualbox

authorize: C:/Users/famig/.ssh/id_rsa.pub

keys:
    - C:/Users/famig/.ssh/id_rsa

folders:
    - map: E:/Progetto/code
      to: /home/vagrant/code
      type: "smb"
      mount_options: ["mfsymlinks,dir_mode=0775,file_mode=0664"]

sites:
    - map: homestead.test
      to: /home/vagrant/code/laravel/public
    - map: bulma.test
      to: /home/vagrant/code/bulma/public
    - map: phpmyadmin.test
      to: /home/vagrant/code/phpMyAdmin

databases:
    - homestead
    - bulma
    - phpmyadmin

# ports:
#     - send: 50000
#       to: 5000
#     - send: 7777
#       to: 777
#       protocol: udp

# blackfire:
#     - id: foo
#       token: bar
#       client-id: foo
#       client-token: bar

# zray:
#  If you've already freely registered Z-Ray, you can place the token here.
#     - email: [email protected]
#       token: foo
#  Don't forget to ensure that you have 'zray: "true"' for your site.

Actual behavior

I can't use Bulma preset and I can't run npm run dev

Steps to reproduce

1. install vagrant
2. install homestead
3. run npm install
4. run npm run dev

Debug LOG

1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'dev' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle @~predev: @
6 info lifecycle @~dev: @
7 verbose lifecycle @~dev: unsafe-perm in lifecycle true
8 verbose lifecycle @~dev: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/vagrant/code/bulma/node_modules/.bin:/home/vagrant/.composer/vendor/bin:/usr/local/go/bin:/home/vagrant/.rbenv/plugins/ruby-build/bin:/home/vagrant/.rbenv/shims:/home/vagrant/.rbenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/vagrant/.dotnet/tools
9 verbose lifecycle @~dev: CWD: /home/vagrant/code/bulma
10 silly lifecycle @~dev: Args: [ '-c', 'npm run development' ]
11 silly lifecycle @~dev: Returned: code: 126  signal: null
12 info lifecycle @~dev: Failed to exec dev script
13 verbose stack Error: @ dev: `npm run development`
13 verbose stack Exit status 126
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:188:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:188:13)
13 verbose stack     at maybeClose (internal/child_process.js:978:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
14 verbose pkgid @
15 verbose cwd /home/vagrant/code/bulma
16 verbose Linux 4.15.0-43-generic
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev"
18 verbose node v11.6.0
19 verbose npm  v6.5.0
20 error code ELIFECYCLE
21 error errno 126
22 error @ dev: `npm run development`
22 error Exit status 126
23 error Failed at the @ dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 126, true ]

Your requirements could not be resolved to an installable set of packages.

why this package not updated, i am using laravel 10 and migrating from bootstrap to bulma..

1st, it's good to have a bulma preset for laravel.

When I do npm run dev with the pageloader extension enabled I get the following error:

resolve-url-loader cannot operate: CSS error
  /Users/user/code/project/resources/assets/sass/app.scss:11014:3: @keyframes missing '}'
  at error (/Users/user/code/project/node_modules/css/lib/parse/index.js:62:15)

Hi,
Did you manage to make Bulma carousel work with Laravel ?
I can't seem to get it done.
Regards

Hello everyone

I have a problem, then I do the installation steps of the package does not load bulma styles, did any of them happend?