Liferay DXP 7.3 Theme Creation: Error during gulp build - sass

I'm getting this error when I try to use the gulp build command:
[09:08:11] Starting 'build:compile-css'...
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($spacer, 2) or calc($spacer / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
╷
306 │ $headings-margin-bottom: $spacer / 2 !default;
│ ^^^^^^^^^^^
╵
build\_css\clay\bootstrap\_variables.scss 306:31 #import
build\_css\clay\base.scss 10:9 #import
build\_css\clay.scss 1:9 root stylesheet
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($input-padding-y, 2) or calc($input-padding-y / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
╷
501 │ $input-height-inner-quarter: add($input-line-height * .25em, $input-padding-y / 2) !default;
│ ^^^^^^^^^^^^^^^^^^^^
╵
build\_css\clay\bootstrap\_variables.scss 501:73 #import
build\_css\clay\base.scss 10:9 #import
build\_css\clay.scss 1:9 root stylesheet
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($custom-control-indicator-size, 2) or calc($custom-control-indicator-size / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
╷
571 │ $custom-switch-indicator-border-radius: $custom-control-indicator-size / 2 !default;
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
build\_css\clay\bootstrap\_variables.scss 571:49 #import
build\_css\clay\base.scss 10:9 #import
build\_css\clay.scss 1:9 root stylesheet
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($spacer, 2) or calc($spacer / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
╷
717 │ $nav-divider-margin-y: $spacer / 2 !default;
│ ^^^^^^^^^^^
╵
build\_css\clay\bootstrap\_variables.scss 717:37 #import
build\_css\clay\base.scss 10:9 #import
build\_css\clay.scss 1:9 root stylesheet
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($spacer, 2) or calc($spacer / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
╷
722 │ $navbar-padding-y: $spacer / 2 !default;
│ ^^^^^^^^^^^
╵
build\_css\clay\bootstrap\_variables.scss 722:37 #import
build\_css\clay\base.scss 10:9 #import
build\_css\clay.scss 1:9 root stylesheet
[09:08:14] 'build:compile-css' errored after 3.14 s
[09:08:14] Error in plugin "sass"
Message:
build\_css\compat\components\_dropdowns.scss
Error: compound selectors may no longer be extended.
Consider `#extend .dropdown-item, .disabled` instead.
╷
34 │ #extend .dropdown-item.disabled;
│ ^^^^^^^^^^^^^^^^^^^^^^^
╵
build\_css\compat\components\_dropdowns.scss 34:11 root stylesheet
Details:
formatted: Error: compound selectors may no longer be extended.
Consider `#extend .dropdown-item, .disabled` instead.
╷
34 │ #extend .dropdown-item.disabled;
│ ^^^^^^^^^^^^^^^^^^^^^^^
╵
build\_css\compat\components\_dropdowns.scss 34:11 root stylesheet
line: 34
column: 11
file: C:\Users\fmateosg\IdeaProjects\test\themes\base-theme\build\_css\compat\components\_dropdowns.scss
status: 1
messageFormatted: build\_css\compat\components\_dropdowns.scss
Error: compound selectors may no longer be extended.
Consider `#extend .dropdown-item, .disabled` instead.
╷
34 │ #extend .dropdown-item.disabled;
│ ^^^^^^^^^^^^^^^^^^^^^^^
╵
build\_css\compat\components\_dropdowns.scss 34:11 root stylesheet
messageOriginal: compound selectors may no longer be extended.
Consider `#extend .dropdown-item, .disabled` instead.
╷
34 │ #extend .dropdown-item.disabled;
│ ^^^^^^^^^^^^^^^^^^^^^^^
╵
build\_css\compat\components\_dropdowns.scss 34:11 root stylesheet
relativePath: build\_css\compat\components\_dropdowns.scss
domainEmitter: [object Object]
domainThrown: false
[09:08:14] 'build' errored after 6.36 s
I know that there is a similar question to this one but the answers there couldn't solve my problem. This is my folder structure:
Folder structure
I copied the _dropdowns.scss file into src/css/compat/components/ and did the modification there but it still gives me the error when I retry to build

I had the same problem because I accidentally upgraded my liferay-theme-tasks in package.json to version 11.2.2.
If thats the case, downgrade liferay-theme-tasks to version ^10.0.2, remove the node_modules folder and run npm install again. Gulp build should pass after that.
I'm using Node.js version 14.17.0, gulp version 4.0.2

Related

ElasticSearch MasterNotDiscoveredException

I've setup an elasticsearch cluster in kuberentes, but I'm getting the error "MasterNotDiscoveredException". I'm not really sure even where to begin debugging this error as there does not appear to be anything really useful in the logs of any of the nodes:
│ elasticsearch {"type": "server", "timestamp": "2022-06-15T00:44:17,226Z", "level": "WARN", "component": "r.suppressed", "cluster.name": "logging-ek", "node.name": "logging-ek-es-master-0", "message": "path: /_bulk, params: {}", │
│ elasticsearch "stacktrace": ["org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized, SERVICE_UNAVAILABLE/2/no master];", │
│ elasticsearch "at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(ClusterBlocks.java:179) ~[elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at org.elasticsearch.action.bulk.TransportBulkAction$BulkOperation.handleBlockExceptions(TransportBulkAction.java:635) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at org.elasticsearch.action.bulk.TransportBulkAction$BulkOperation.doRun(TransportBulkAction.java:481) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at org.elasticsearch.action.bulk.TransportBulkAction$BulkOperation$2.onTimeout(TransportBulkAction.java:669) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:345) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:263) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:660) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:718) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]", │
│ elasticsearch "at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]", │
│ elasticsearch "at java.lang.Thread.run(Thread.java:833) [?:?]", │
│ elasticsearch "Suppressed: org.elasticsearch.discovery.MasterNotDiscoveredException", │
│ elasticsearch "\tat org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$2.onTimeout(TransportMasterNodeAction.java:297) ~[elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "\tat org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:345) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "\tat org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:263) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "\tat org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:660) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "\tat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:718) [elasticsearch-7.17.1.jar:7.17.1]", │
│ elasticsearch "\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]", │
│ elasticsearch "\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]", │
│ elasticsearch "\tat java.lang.Thread.run(Thread.java:833) [?:?]"] }
is pretty much the only logs i've ever seen.
It does appear that the cluster sees all of my master nodes:
elasticsearch {"type": "server", "timestamp": "2022-06-15T00:45:41,915Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "logging-ek", "node.name": "logging-ek-es-master-0", "message": "master not discovered yet, this node has not previously joine │
│ d a bootstrapped (v7+) cluster, and [cluster.initial_master_nodes] is empty on this node: have discovered [{logging-ek-es-master-0}{fHLQrvLsTJ6UvR_clSaxfg}{iLoGrnWSTpiZxq59z7I5zA}{10.42.64.4}{10.42.64.4:9300}{mr}, {logging-ek-es-master-1}{EwF8WLIgSF6Q1Q46_51VlA}{wz5rg74iThicJdtzXZg29g}{ │
│ 10.42.240.8}{10.42.240.8:9300}{mr}, {logging-ek-es-master-2}{jtrThk_USA2jUcJYoIHQdg}{HMvZ_dUfTM-Ar4ROeIOJlw}{10.42.0.5}{10.42.0.5:9300}{mr}]; discovery will continue using [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, 127.0.0.1:9305, [::1]:9300, [::1]: │
│ 9301, [::1]:9302, [::1]:9303, [::1]:9304, [::1]:9305, 10.42.0.5:9300, 10.42.240.8:9300] from hosts providers and [{logging-ek-es-master-0}{fHLQrvLsTJ6UvR_clSaxfg}{iLoGrnWSTpiZxq59z7I5zA}{10.42.64.4}{10.42.64.4:9300}{mr}] from last-known cluster state; node term 0, last-accepted version │
│ 0 in term 0" }
and I've verified that they can in fact reach each other through the network. Is there anything else or anywhere else I need to look for errors? I installed elasticsearch via elasticoperator.
Start doing curl to the 9300 port. Make sure you get a valid response going both ways.
Also make sure your MTU is set right or this can happen as well. It's a network problem most of the time.

Send an email when application shuts down

I need to send an email when the application shuts down.
I have created the following method:
void onStop(#Observes ShutdownEvent event) throws ParserConfigurationException {
mailer.send(Mail.withText("test#email.com","STOP TEST", "HERE IS STOP A TEST"));
Quarkus.waitForExit();
}
But I always receive the following error:
│ Caused by: java.net.ConnectException: Connection refused (Connection refused) │
│ at java.base/java.net.PlainSocketImpl.socketConnect(Native Method) │
│ at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412) │
│ at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255) │
│ at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237) │
│ at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) │
│ at java.base/java.net.Socket.connect(Socket.java:609) │
│ at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:368) │
│ at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) │
│ ... 32 more
I am quite sure that all the connections are closed when I am trying to send the email. This is very similar to the question asked here -> How to accept http requests after shutdown signal in Quarkus?, but not clear to me how to implement the solution he proposes.
Any help is greatly appreciated.

Why am I getting an error when using Sass with AgGrid in laravel?

an error is happening to me when following the guide of Ag-Grid vue (https://www.ag-grid.com/vuejs-grid/#vue_theme_look)
When I use the normal styles I have no problem.
Error:
Uncaught Error: Module build failed (from ./node_modules/css-loader/index.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
-webkit-font-smoothing: antialiased;
^
Declarations may only be used within style rules.
╷
29 │ -webkit-font-smoothing: antialiased;
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
node_modules\ag-grid-community\src\styles\ag-theme-base\sass\_ag-theme-base-mixin.scss 29:5 ag-theme-base()
node_modules\ag-grid-community\src\styles\ag-theme-alpine\sass\_ag-theme-alpine-mixin.scss 8:5 ag-theme-alpine()
resources\sass\_aggrid.scss 4:1 #import
stdin 12:9 root stylesheet
in C:\laragon\www\zonadolar\node_modules\ag-grid-community\src\styles\ag-theme-base\sass\_ag-theme-base-mixin.scss (line 29, column 5)
at C:\laragon\www\zonadolar\node_modules\webpack\lib\NormalModule.js:316:20
at C:\laragon\www\zonadolar\node_modules\loader-runner\lib\LoaderRunner.js:367:11
at C:\laragon\www\zonadolar\node_modules\loader-runner\lib\LoaderRunner.js:233:18
at context.callback (C:\laragon\www\zonadolar\node_modules\loader-runner\lib\LoaderRunner.js:111:13)
at C:\laragon\www\zonadolar\node_modules\sass-loader\dist\index.js:89:7
at Function.call$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:88191:16)
at _render_closure1.call$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:77610:12)
at _RootZone.runBinary$3$3 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:26152:18)
at _RootZone.runBinary$3 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:26156:19)
at _FutureListener.handleError$1 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24600:19)
at _Future__propagateToListeners_handleError.call$0 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24897:40)
at Object._Future__propagateToListeners (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:4311:88)
at _Future._completeError$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24725:9)
at _AsyncAwaitCompleter.completeError$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24117:12)
at Object._asyncRethrow (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:4065:17)
at C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:14087:20
at _wrapJsFunctionForAsync_closure.$protected (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:4090:15)
at _wrapJsFunctionForAsync_closure.call$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24138:12)
at _awaitOnObject_closure0.call$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24130:25)
at _RootZone.runBinary$3$3 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:26152:18)
at _RootZone.runBinary$3 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:26156:19)
at _FutureListener.handleError$1 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24600:19)
at _Future__propagateToListeners_handleError.call$0 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24897:40)
at Object._Future__propagateToListeners (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:4311:88)
at _Future._completeError$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24725:9)
at _AsyncAwaitCompleter.completeError$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24117:12)
at Object._asyncRethrow (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:4065:17)
at C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:16672:20
at _wrapJsFunctionForAsync_closure.$protected (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:4090:15)
at _wrapJsFunctionForAsync_closure.call$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24138:12)
at _awaitOnObject_closure0.call$2 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24130:25)
at _RootZone.runBinary$3$3 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:26152:18)
at _RootZone.runBinary$3 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:26156:19)
at _FutureListener.handleError$1 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24600:19)
at _Future__propagateToListeners_handleError.call$0 (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:24897:40)
at Object._Future__propagateToListeners (C:\laragon\www\zonadolar\node_modules\sass\sass.dart.js:4311:88)
at Object../resources/sass/app.scss (http://zonadolar.test/js/app.js:81476:7)
at __webpack_require__ (http://zonadolar.test/js/app.js:20:30)
at Object.0 (http://zonadolar.test/js/app.js:81488:18)
at __webpack_require__ (http://zonadolar.test/js/app.js:20:30)
at http://zonadolar.test/js/app.js:84:18
at http://zonadolar.test/js/app.js:87:10
./resources/sass/app.scss # app.js:81476
__webpack_require__ # app.js:20
0 # app.js:81488
__webpack_require__ # app.js:20
(anonymous) # app.js:84
(anonymous) # app.js:87
resources/sass/_aggrid.scss
#import "../../node_modules/ag-grid-community/src/styles/ag-grid.scss";
#import "../../node_modules/ag-grid-community/src/styles/ag-theme-alpine/sass/ag-theme-alpine-mixin.scss";
#include ag-theme-alpine((
add-row-background-color: #ACE
));
apparently when commenting #include the error disappears
Laravel 6
Windows 10 with Laragon (Local)
Already solved.
Apparently the documentation is wrong.
It is not add-row-background-color: #ACE it should be odd-row-background-color: #ACE

Empty karma html report

Here are the facts:
I have a nodejs app
I've written some Jasmine tests
I'm using karma to generate the code coverage report
Here is the karma.conf.js:
module.exports = function (config) {
config.set({
frameworks: ['jasmine', 'browserify'],
files: [
'utils/dates.js',
'utils/maths.js',
'spec/server_utils_spec.js'
],
preprocessors: {
'utils/*.js': ['coverage', 'browserify'],
'spec/server_utils_spec.js': ['coverage', 'browserify']
},
reporters: ['progress', 'coverage'],
coverageReporter: {
type: 'html',
dir: 'coverage/'
},
colors: true,
logLevel: config.LOG_INFO,
autoWatch: true,
singleRun: false
})
}
These are my packages (I know they are global):
→ npm -g list | grep -i "karma"
├─┬ karma#2.0.4
├─┬ karma-browserify#5.3.0
├─┬ karma-coverage#1.1.2
├─┬ karma-html-reporter#0.2.7
├── karma-jasmine#1.1.2
├─┬ karma-mocha#1.3.0
and despite the terminal log
/usr/bin/karma start server/karma.conf.js
23 07 2018 15:39:36.033:INFO [framework.browserify]: registering rebuild (autoWatch=true)
23 07 2018 15:39:36.817:INFO [framework.browserify]: 3073 bytes written (0.03 seconds)
23 07 2018 15:39:36.817:INFO [framework.browserify]: bundle built
23 07 2018 15:39:36.818:WARN [karma]: No captured browser, open http://localhost:9876/
23 07 2018 15:39:36.822:INFO [karma]: Karma v2.0.4 server started at http://0.0.0.0:9876/
23 07 2018 15:39:39.135:INFO [Chrome 67.0.3396 (Linux 0.0.0)]: Connected on socket H9J96y-fFn-7PfkHAAAA with id manual-9692
Chrome 67.0.3396 (Linux 0.0.0): Executed 0 of 2 SUCCESS (0 secs / 0 secs)
Chrome 67.0.3396 (Linux 0.0.0): Executed 1 of 2 SUCCESS (0 secs / 0.001 secs)
Chrome 67.0.3396 (Linux 0.0.0): Executed 2 of 2 SUCCESS (0 secs / 0.002 secs)
Chrome 67.0.3396 (Linux 0.0.0): Executed 2 of 2 SUCCESS (0.033 secs / 0.002 secs)
TOTAL: 2 SUCCESS
I get this result when I open the generated html report:
I've tried the solutions to all the other related questions and I've come up with nothing.
My questions:
why the empty report?
how can I manage to have the report
Thank you in advance!

running gulp inside a Laravel project fails when mixing styles and/or compiling sass files

Everything was working and i was capable to run gulp and gulp watch normally, after some changes in my phpspec files it dosn't work anymore. See the details below.
This is my gulpfile.js
var elixir = require('laravel-elixir');
elixir(function (mix) {
mix.phpUnit().phpSpec();
// this task should look for files inside the resources/assets/sass
// folder.
mix.sass(
[
'./resources/assets/bower/bootstrap-sass/assets/stylesheets/_bootstrap.scss',
'**',
],
'resources/assets/css/sass.css'
);
// this task should look for files inside the resources/assets/css
// folder.
mix.styles(
[
'**',
],
'public/css/all.css'
);
// this task should look for files inside the resources/assets/js
// folder.
mix.scripts(
[
'./resources/assets/bower/jquery/dist/jquery.js',
'./resources/assets/bower/bootstrap-sass/assets/javascripts/bootstrap.js',
'**',
],
'public/js/app.js'
);
mix.version(
[
"css/all.css",
"js/app.js",
]
);
mix.browserSync(
{
proxy: "localhost:8000",
}
);
});
And this is the output after runing gulp:
[19:00:44] Using gulpfile ~/Public/forsale/gulpfile.js
[19:00:44] Starting 'default'...
[19:00:44] Starting 'PHPUnit'...
Triggering PHPUnit: vendor/bin/phpunit --verbose
[19:00:44] Finished 'default' after 44 ms
PHPUnit 4.8.26 by Sebastian Bergmann and contributors.
Runtime: PHP 7.0.4-7ubuntu2.1
Configuration: /home/rafael/Public/forsale/phpunit.xml
.
Time: 49 ms, Memory: 8.00MB
OK (1 test, 1 assertion)
[19:00:44] gulp-notify: [Green!] Your PHPUnit tests passed!
[19:00:44] Finished 'PHPUnit' after 144 ms
[19:00:44] Starting 'PHPSpec'...
Triggering PHPSpec: vendor/bin/phpspec run
/ skipped: 0% / pending: 0% / passed: 100% / failed: 0% / broken: 0% / 2 examples
1 specs
2 examples (2 passed)
5ms
[19:00:44] gulp-notify: [Green!] Your PHPSpec tests passed!
[19:00:44] Finished 'PHPSpec' after 84 ms
[19:00:44] Starting 'sass'...
Fetching Sass Source Files...
- ./resources/assets/bower/bootstrap-sass/assets/stylesheets/_bootstrap.scss
Saving To...
- resources/assets/css/sass.css
[19:00:44] 'sass' errored after 104 ms
[19:00:44] Error: Cannot find module './flex-Spec'
at Function.Module._resolveFilename (module.js:326:15)
at Function.Module._load (module.js:277:25)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/home/rafael/Public/forsale/node_modules/autoprefixer-core/lib/hacks/flex.js:6:14)
at Object.<anonymous> (/home/rafael/Public/forsale/node_modules/autoprefixer-core/lib/hacks/flex.js:58:4)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
[19:00:44] Error in plugin 'run-sequence(sass)'
Message:
sass catch
It seems that run-sequence has a missing module, but i didn't find it.
The problem was solved, i removed my node_modules folder and applied npm install && npm update again. It looks like one of my libraries were damaged and i don't know why.

Resources