I started a m.e.a.n. server with google compute engine. It seems ok but should it be this slow? The server is http://130.211.66.116:3000/
Everything seems ok but the response time is like 30 seconds. Is it just that the example configuration has too little power and I must create a new VM with more dedicated power? I used the example from google.
How I start it:
$ gulp
Invoking gulp - development
[08:04:58] Using gulpfile ~/onacciweb/gulpfile.js
[08:04:58] Starting 'clean'...
[08:04:58] Finished 'clean' after 4.95 ms
[08:04:58] Starting 'default'...
[08:04:58] Starting 'coffee'...
[08:04:58] Finished 'coffee' after 7.29 ms
[08:04:58] Starting 'clean'...
[08:04:58] Starting 'less'...
[08:04:58] Starting 'csslint'...
[08:04:58] Starting 'env:development'...
[08:04:58] Finished 'env:development' after 33 μs
[08:04:58] Starting 'devServe'...
[08:04:58] Finished 'devServe' after 65 ms
[08:04:58] Starting 'watch'...
[08:05:04] Finished 'watch' after 5.31 s
[08:05:04] Finished 'clean' after 5.62 s
[08:05:04] [nodemon] v1.4.1
[08:05:04] [nodemon] to restart at any time, enter `rs`
[08:05:04] [nodemon] watching: *.*
[08:05:04] [nodemon] starting `node --debug server.js`
debugger listening on port 5858
[08:05:05]
[08:05:05] Finished 'less' after 6.53 s
[08:05:05] csslint: 3 files lint free
[08:05:05] Finished 'csslint' after 6.35 s
[08:05:05] Starting 'development'...
[08:05:05] Finished 'development' after 12 μs
loading docs for: /home/niklasro/onacciweb/packages/core/articles
Mean app started on port 3000 (development) cluster.worker.id: 0
[08:05:07] index.html reloaded.
It looks like your issue is that livereload.js is timing out. On that Click to Deploy, I believe there are some post deployment steps that must be completed for final configuration of the MEAN instance. Did you successfully complete those?
Related
I am building an application customizer for our SharePoint online site, but i keep getting this error:-
Error - [package-solution] No manifests were found in 'D:/extensionForFullstack/extension-for-fullstack/release/manifests'. Ensure a build has completed successfully
when i run gulp package-solution --ship. here is the full outputs from creating the solution till getting the error:-
D:\>md extensionForFullstack
D:\>cd D:\extensionForFullstack
D:\extensionForFullstack>yo #microsoft/sharepoint
_-----_ ╭──────────────────────────╮
| | │ Welcome to the │
|--(o)--| │ SharePoint Client-side │
`---------´ │ Solution │
( _´U`_ ) │ Generator#1.13.0 │
/___A___\ /╰──────────────────────────╯
| ~ |
__'.___.'__
´ ` |° ´ Y `
Let's create a new SharePoint solution.
? What is your solution name? extension-for-fullstack
? Only SharePoint Online (latest) is supported. For earlier versions of SharePoint (2016 and 2019) please use the 1.4.1 version of the generator. SharePoint Online only (latest)
? Where do you want to place the files? Create a subfolder with solution name
? Do you want to allow the tenant admin the choice of being able to deploy the solution to all sites immediately without running any feature deployment or adding apps in sites? Yes
? Will the components in the solution require permissions to access web APIs that are unique and not shared with other components in the tenant? Yes
? Which type of client-side component to create? Extension
? Which type of client-side extension to create? Application Customizer
Add new Application Customizer to solution extension-for-fullstack.
? What is your Application Customizer name? HelloWorld
? What is your Application Customizer description? HelloWorld description
force .yo-rc.json
force extension-for-fullstack\.yo-rc.json
create extension-for-fullstack\config\package-solution.json
create extension-for-fullstack\package.json
create extension-for-fullstack\config\config.json
create config\serve.json
create extension-for-fullstack\tsconfig.json
create extension-for-fullstack\.vscode\extensions.json
create extension-for-fullstack\.vscode\launch.json
create extension-for-fullstack\.vscode\settings.json
create extension-for-fullstack\config\deploy-azure-storage.json
create extension-for-fullstack\config\serve.json
create extension-for-fullstack\config\write-manifests.json
create extension-for-fullstack\src\index.ts
create extension-for-fullstack\gulpfile.js
create extension-for-fullstack\README.md
create extension-for-fullstack\tslint.json
create extension-for-fullstack\.gitignore
create extension-for-fullstack\.npmignore
create src\extensions\helloWorld\HelloWorldApplicationCustomizer.ts
create src\extensions\helloWorld\loc\en-us.js
create src\extensions\helloWorld\loc\myStrings.d.ts
create src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
create sharepoint\assets\ClientSideInstance.xml
create sharepoint\assets\elements.xml
No change to package.json was detected. No package manager install will be executed.
_=+#####!
###########| .------------------------------------------------.
###/ (##|(#) | Congratulations! |
### ######| \ | Solution extension-for-fullstack is created. |
###/ /###| (#) | Run gulp serve to play with it! |
####### ##| / '------------------------------------------------'
### /##|(#)
###########|
**=+####!
D:\extensionForFullstack>code .
D:\extensionForFullstack>cd D:\extensionForFullstack\extension-for-fullstack
D:\extensionForFullstack\extension-for-fullstack>Gulp build
[11:47:56] Local modules not found in D:\extensionForFullstack\extension-for-fullstack
[11:47:56] Try running: npm install
D:\extensionForFullstack\extension-for-fullstack> npm install
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated tslint#6.1.3: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated #types/anymatch#3.0.0: This is a stub types definition. anymatch provides its own type definitions, so you do not need this installed.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request-promise-native#1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated left-pad#1.3.0: use String.prototype.padStart()
npm WARN deprecated #opentelemetry/types#0.2.0: Package renamed to #opentelemetry/api, see https://github.com/open-telemetry/opentelemetry-js
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.1.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated sane#4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated tar#2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated fsevents#2.1.3: "Please update to latest v2.3 or v2.2"
npm WARN deprecated svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
> node-sass#4.14.1 install D:\extensionForFullstack\extension-for-fullstack\node_modules\node-sass
> node scripts/install.js
Cached binary found at C:\Users\**\AppData\Roaming\npm-cache\node-sass\4.14.1\win32-x64-83_binding.node
> es5-ext#0.10.61 postinstall D:\extensionForFullstack\extension-for-fullstack\node_modules\es5-ext
> node -e "try{require('./_postinstall')}catch(e){}" || exit 0
> node-sass#4.14.1 postinstall D:\extensionForFullstack\extension-for-fullstack\node_modules\node-sass
> node scripts/build.js
Binary found at D:\extensionForFullstack\extension-for-fullstack\node_modules\node-sass\vendor\win32-x64-83\binding.nodeTesting binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^2.1.2 (node_modules\jest-haste-map\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.1.2 (node_modules\#rushstack\typings-generator\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN office-ui-fabric-react#7.176.2 requires a peer of #types/react#>=16.8.0 <17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN office-ui-fabric-react#7.176.2 requires a peer of #types/react-dom#>=16.8.0 <17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #fluentui/theme#1.7.6 requires a peer of #types/react#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #fluentui/theme#1.7.6 requires a peer of #types/react-dom#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #uifabric/utilities#7.34.1 requires a peer of #types/react#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #uifabric/utilities#7.34.1 requires a peer of #types/react-dom#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #fluentui/react-focus#7.18.4 requires a peer of #types/react#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #fluentui/react-focus#7.18.4 requires a peer of #types/react-dom#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #fluentui/react-window-provider#1.0.3 requires a peer of #types/react#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #fluentui/react-window-provider#1.0.3 requires a peer of #types/react-dom#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #uifabric/react-hooks#7.14.2 requires a peer of #types/react#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #uifabric/react-hooks#7.14.2 requires a peer of #types/react-dom#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #uifabric/foundation#7.10.3 requires a peer of #types/react#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #uifabric/foundation#7.10.3 requires a peer of #types/react-dom#>=16.8.0 <18.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ajv-keywords#3.5.2 requires a peer of ajv#^6.9.1 but none is installed. You must install peer dependencies yourself.
added 2240 packages from 1001 contributors and audited 2246 packages in 343.341s
123 packages are looking for funding
run `npm fund` for details
found 120 vulnerabilities (20 low, 55 moderate, 42 high, 3 critical)
run `npm audit fix` to fix them, or `npm audit` for details
D:\extensionForFullstack\extension-for-fullstack>Gulp build
Build target: DEBUG
[11:54:45] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[11:54:45] Starting 'build'...
[11:54:45] Starting gulp
[11:54:45] Starting subtask 'pre-copy'...
[11:54:45] Finished subtask 'pre-copy' after 127 ms
[11:54:45] Starting subtask 'copy-static-assets'...
[11:54:45] Starting subtask 'sass'...
[11:54:45] Finished subtask 'copy-static-assets' after 21 ms
[11:54:45] Finished subtask 'sass' after 12 ms
[11:54:45] Starting subtask 'tslint'...
[11:54:46] [tslint] tslint version: 5.20.1
[11:54:46] Starting subtask 'tsc'...
[11:54:46] [tsc] typescript version: 3.9.10
[11:54:46] Finished subtask 'tsc' after 867 ms
[11:54:47] Finished subtask 'tslint' after 1.37 s
[11:54:47] Starting subtask 'post-copy'...
[11:54:47] Finished subtask 'post-copy' after 211 μs
[11:54:47] Finished 'build' after 1.52 s
[11:54:47] ==================[ Finished ]==================
[11:54:48] Project extension-for-fullstack version:0.0.1
[11:54:48] Build tools version:3.17.17
[11:54:48] Node version:v14.18.1
[11:54:48] Total duration:20 s
D:\extensionForFullstack\extension-for-fullstack>Gulp bundle -ship
Usage: gulp [options] tasks
Options:
--help, -h Show this help. [boolean]
--version, -v Print the global and local gulp versions. [boolean]
--require Will require a module before running the gulpfile.
This is useful for transpilers but also has other
applications. [string]
--gulpfile, -f Manually set path of gulpfile. Useful if you have
multiple gulpfiles. This will set the CWD to the
gulpfile directory as well. [string]
--cwd Manually set the CWD. The search for the gulpfile, as
well as the relativity of all requires will be from
here. [string]
--verify Will verify plugins referenced in project's
package.json against the plugins blacklist.
--tasks, -T Print the task dependency tree for the loaded
gulpfile. [boolean]
--tasks-simple Print a plaintext list of tasks for the loaded
gulpfile. [boolean]
--tasks-json Print the task dependency tree, in JSON format, for
the loaded gulpfile.
--tasks-depth, --depth Specify the depth of the task dependency tree.[number]
--compact-tasks Reduce the output of task dependency tree by printing
only top tasks and their child tasks. [boolean]
--sort-tasks Will sort top tasks of task dependency tree. [boolean]
--color Will force gulp and gulp plugins to display colors,
even when no color support is detected. [boolean]
--no-color Will force gulp and gulp plugins to not display
colors, even when color support is detected. [boolean]
--silent, -S Suppress all gulp logging. [boolean]
--continue Continue execution of tasks upon failure. [boolean]
--series Run tasks given on the CLI in series (the default is
parallel). [boolean]
--log-level, -L Set the loglevel. -L for least verbose and -LLLL for
most verbose. -LLL is default. [count]
D:\extensionForFullstack\extension-for-fullstack>Gulp bundle --ship
Build target: SHIP
[11:54:58] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[11:54:58] Starting 'bundle'...
[11:54:58] Starting gulp
[11:54:58] Starting subtask 'pre-copy'...
[11:54:58] Finished subtask 'pre-copy' after 66 ms
[11:54:58] Starting subtask 'copy-static-assets'...
[11:54:58] Starting subtask 'sass'...
[11:54:58] Finished subtask 'copy-static-assets' after 28 ms
[11:54:58] Finished subtask 'sass' after 16 ms
[11:54:58] Starting subtask 'tslint'...
[11:54:58] [tslint] tslint version: 5.20.1
[11:54:58] Starting subtask 'tsc'...
[11:54:58] [tsc] typescript version: 3.9.10
[11:54:58] Finished subtask 'tsc' after 780 ms
[11:54:59] Finished subtask 'tslint' after 951 ms
[11:54:59] Starting subtask 'post-copy'...
[11:54:59] Finished subtask 'post-copy' after 1.53 ms
[11:54:59] Starting subtask 'configure-webpack'...
[11:54:59] Error - 'configure-webpack' sub task errored after 199 ms
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
ENOENT: no such file or directory, open 'D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json'
[11:54:59] 'bundle' errored after 1.26 s
[11:54:59]
About to exit with code: 1
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1
D:\extensionForFullstack\extension-for-fullstack>Gulp package-solution --ship
Build target: SHIP
[11:55:09] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[11:55:09] Starting 'package-solution'...
[11:55:09] Starting gulp
[11:55:09] Starting subtask 'package-solution'...
[11:55:10] Error - [package-solution] No manifests were found in 'D:\extensionForFullstack\extension-for-fullstack\release/manifests'. Ensure a build has completed successfully
[11:55:10] Finished subtask 'package-solution' after 33 ms
[11:55:10] Finished 'package-solution' after 38 ms
[11:55:10] ==================[ Finished ]==================
Error - [package-solution] No manifests were found in 'D:/extensionForFullstack/extension-for-fullstack/release/manifests'. Ensure a build has completed successfully
[11:55:11] Project extension-for-fullstack version:0.0.1
[11:55:11] Build tools version:3.17.17
[11:55:11] Node version:v14.18.1
[11:55:11] Total duration:3.31 s
[11:55:11] Task errors:1
The build failed because a task wrote output to stderr.
Exiting with exit code: 1
D:\extensionForFullstack\extension-for-fullstack>gulp bundle
Build target: DEBUG
[11:57:10] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[11:57:10] Starting 'bundle'...
[11:57:10] Starting gulp
[11:57:10] Starting subtask 'pre-copy'...
[11:57:10] Finished subtask 'pre-copy' after 47 ms
[11:57:10] Starting subtask 'copy-static-assets'...
[11:57:10] Starting subtask 'sass'...
[11:57:10] Finished subtask 'copy-static-assets' after 20 ms
[11:57:10] Finished subtask 'sass' after 11 ms
[11:57:10] Starting subtask 'tslint'...
[11:57:10] [tslint] tslint version: 5.20.1
[11:57:10] Starting subtask 'tsc'...
[11:57:10] [tsc] typescript version: 3.9.10
[11:57:11] Finished subtask 'tsc' after 727 ms
[11:57:11] Finished subtask 'tslint' after 856 ms
[11:57:11] Starting subtask 'post-copy'...
[11:57:11] Finished subtask 'post-copy' after 206 μs
[11:57:11] Starting subtask 'configure-webpack'...
[11:57:11] Error - 'configure-webpack' sub task errored after 185 ms
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
ENOENT: no such file or directory, open 'D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json'
[11:57:11] 'bundle' errored after 1.12 s
[11:57:11]
About to exit with code: 1
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1
D:\extensionForFullstack\extension-for-fullstack>gulp package-solution --ship
Build target: SHIP
[11:57:32] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[11:57:32] Starting 'package-solution'...
[11:57:32] Starting gulp
[11:57:32] Starting subtask 'package-solution'...
[11:57:32] Error - [package-solution] No manifests were found in 'D:\extensionForFullstack\extension-for-fullstack\release/manifests'. Ensure a build has completed successfully
[11:57:32] Finished subtask 'package-solution' after 19 ms
[11:57:32] Finished 'package-solution' after 24 ms
[11:57:33] ==================[ Finished ]==================
Error - [package-solution] No manifests were found in 'D:/extensionForFullstack/extension-for-fullstack/release/manifests'. Ensure a build has completed successfully
[11:57:33] Project extension-for-fullstack version:0.0.1
[11:57:33] Build tools version:3.17.17
[11:57:33] Node version:v14.18.1
[11:57:33] Total duration:3.3 s
[11:57:33] Task errors:1
The build failed because a task wrote output to stderr.
Exiting with exit code: 1
D:\extensionForFullstack\extension-for-fullstack>gulp bundle --ship
Build target: SHIP
[12:00:07] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[12:00:07] Starting 'bundle'...
[12:00:07] Starting gulp
[12:00:07] Starting subtask 'pre-copy'...
[12:00:07] Finished subtask 'pre-copy' after 58 ms
[12:00:07] Starting subtask 'copy-static-assets'...
[12:00:07] Starting subtask 'sass'...
[12:00:07] Finished subtask 'copy-static-assets' after 28 ms
[12:00:07] Finished subtask 'sass' after 16 ms
[12:00:07] Starting subtask 'tslint'...
[12:00:07] [tslint] tslint version: 5.20.1
[12:00:07] Starting subtask 'tsc'...
[12:00:07] [tsc] typescript version: 3.9.10
[12:00:08] Finished subtask 'tsc' after 745 ms
[12:00:08] Finished subtask 'tslint' after 892 ms
[12:00:08] Starting subtask 'post-copy'...
[12:00:08] Finished subtask 'post-copy' after 1.35 ms
[12:00:08] Starting subtask 'configure-webpack'...
[12:00:08] Error - 'configure-webpack' sub task errored after 165 ms
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
ENOENT: no such file or directory, open 'D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json'
[12:00:08] 'bundle' errored after 1.16 s
[12:00:08]
About to exit with code: 1
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1
D:\extensionForFullstack\extension-for-fullstack>gulp clean
Build target: DEBUG
[12:00:24] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[12:00:24] Starting 'clean'...
[12:00:24] Starting gulp
[12:00:24] Starting subtask 'clean'...
[12:00:24] Finished subtask 'clean' after 7.45 ms
[12:00:24] Finished 'clean' after 12 ms
[12:00:24] ==================[ Finished ]==================
[12:00:25] Project extension-for-fullstack version:0.0.1
[12:00:25] Build tools version:3.17.17
[12:00:25] Node version:v14.18.1
[12:00:25] Total duration:3.47 s
D:\extensionForFullstack\extension-for-fullstack>gulp bundle --ship
Build target: SHIP
[12:00:36] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[12:00:36] Starting 'bundle'...
[12:00:36] Starting gulp
[12:00:36] Starting subtask 'pre-copy'...
[12:00:36] Finished subtask 'pre-copy' after 55 ms
[12:00:36] Starting subtask 'copy-static-assets'...
[12:00:36] Starting subtask 'sass'...
[12:00:36] Finished subtask 'copy-static-assets' after 32 ms
[12:00:36] Finished subtask 'sass' after 19 ms
[12:00:36] Starting subtask 'tslint'...
[12:00:36] [tslint] tslint version: 5.20.1
[12:00:36] Starting subtask 'tsc'...
[12:00:36] [tsc] typescript version: 3.9.10
[12:00:36] Finished subtask 'tsc' after 760 ms
[12:00:37] Finished subtask 'tslint' after 908 ms
[12:00:37] Starting subtask 'post-copy'...
[12:00:37] Finished subtask 'post-copy' after 1.38 ms
[12:00:37] Starting subtask 'configure-webpack'...
[12:00:37] Error - 'configure-webpack' sub task errored after 166 ms
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
ENOENT: no such file or directory, open 'D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json'
[12:00:37] 'bundle' errored after 1.18 s
[12:00:37]
About to exit with code: 1
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1
D:\extensionForFullstack\extension-for-fullstack>gulp bundle --ship
Build target: SHIP
[12:03:06] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[12:03:06] Starting 'bundle'...
[12:03:06] Starting gulp
[12:03:06] Starting subtask 'pre-copy'...
[12:03:06] Finished subtask 'pre-copy' after 45 ms
[12:03:06] Starting subtask 'copy-static-assets'...
[12:03:06] Starting subtask 'sass'...
[12:03:06] Finished subtask 'copy-static-assets' after 20 ms
[12:03:06] Finished subtask 'sass' after 11 ms
[12:03:06] Starting subtask 'tslint'...
[12:03:06] [tslint] tslint version: 5.20.1
[12:03:06] Starting subtask 'tsc'...
[12:03:06] [tsc] typescript version: 3.9.10
[12:03:07] Finished subtask 'tsc' after 733 ms
[12:03:07] Finished subtask 'tslint' after 886 ms
[12:03:07] Starting subtask 'post-copy'...
[12:03:07] Finished subtask 'post-copy' after 1.35 ms
[12:03:07] Starting subtask 'configure-webpack'...
[12:03:07] Error - 'configure-webpack' sub task errored after 163 ms
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
File does not exist: D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json
ENOENT: no such file or directory, open 'D:\extensionForFullstack\extension-for-fullstack\src\extensions\helloWorld\HelloWorldApplicationCustomizer.manifest.json'
[12:03:07] 'bundle' errored after 1.13 s
[12:03:07]
About to exit with code: 1
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1
D:\extensionForFullstack\extension-for-fullstack>gulp package-solution --ship
Build target: SHIP
[12:03:13] Using gulpfile D:\extensionForFullstack\extension-for-fullstack\gulpfile.js
[12:03:13] Starting 'package-solution'...
[12:03:13] Starting gulp
[12:03:13] Starting subtask 'package-solution'...
[12:03:13] Error - [package-solution] No manifests were found in 'D:\extensionForFullstack\extension-for-fullstack\release/manifests'. Ensure a build has completed successfully
[12:03:13] Finished subtask 'package-solution' after 14 ms
[12:03:13] Finished 'package-solution' after 18 ms
[12:03:14] ==================[ Finished ]==================
Error - [package-solution] No manifests were found in 'D:/extensionForFullstack/extension-for-fullstack/release/manifests'. Ensure a build has completed successfully
[12:03:14] Project extension-for-fullstack version:0.0.1
[12:03:14] Build tools version:3.17.17
[12:03:14] Node version:v14.18.1
[12:03:14] Total duration:3.23 s
[12:03:14] Task errors:1
The build failed because a task wrote output to stderr.
Exiting with exit code: 1
D:\extensionForFullstack\extension-for-fullstack>
It looks like there is a problem with app customzier project generated if you select "create a solution subfolder" in the version 1.13 of the wizard (a bug). Some required folders are created in the root folder, even if you select "use subfolder" option. These folders include the manifest folder.
To fix the things you could:
use the latest version (1.14) of SPFx tools. Version 1.14 does not provide the subfolder option anymore, so you won't be able to select it, and there should be no problem :)
Alternatively, select "use current folder" (default) when creating a project using 1.13 wizard, not "create subfolder". Should also work.
Just like the title, I currently have a nasty problem with Gulp watch, that keeps on compiling my files even though there aren't any change made.
For instance, this is a piece of my 'watch' task
gulp.task('watch', function() {
gulp.watch(jsIn, ['babel']);
}
And my 'babel' task, just to compile my scripts and move them to dist folder
const jsIn = ['dev/scripts/*.js', 'dev/scripts/**/*.js'],
jsOut = 'dist/scripts';
gulp.task('babel', function() {
gulp.src(jsIn)
.pipe(babel())
.on('error', gutil.log)
.pipe(gulp.dest(jsOut))
.pipe(connect.reload()); //yes I use gulp-connect to live reload my files.
});
When I run gulp watch it works normally, and then this keeps on happening
TRUONGs-MacBook-Pro:code sdsmnc$ gulp watch
[14:48:31] Using gulpfile /Volumes/SDSMNC_BU/2018/wildlife/code/gulpfile.js
[14:48:31] Starting 'watch'...
[14:48:31] Finished 'watch' after 14 ms
[14:48:32] Starting 'babel'...
[14:48:32] Finished 'babel' after 14 ms
[14:48:34] Starting 'babel'...
[14:48:34] Finished 'babel' after 1.95 ms
[14:48:34] Starting 'babel'...
[14:48:34] Finished 'babel' after 1.5 ms
[14:48:37] Starting 'babel'...
[14:48:37] Finished 'babel' after 1.18 ms
[14:48:39] Starting 'babel'...
[14:48:39] Finished 'babel' after 1.07 ms
[14:48:41] Starting 'babel'...
[14:48:41] Finished 'babel' after 1.03 ms
[14:48:42] Starting 'babel'...
[14:48:42] Finished 'babel' after 1.73 ms
[14:48:44] Starting 'babel'...
[14:48:44] Finished 'babel' after 1.04 ms
I practically use the same gulpfile.js for all of my projects, the old ones work fine, but somehow in this new project I get this problem. I tried to delete the node_modules folder and reinstall all the dependencies, even use the node_modules of my old projects but can't fix the problem.
Any help please...?
I've got a gulpfile set up with both a series of tasks to bundle an Angular2 app using systemjs as well as with webpack. Unfortunately, I'm seeing that if I run one of them in my Powershell prompt (e.g. "gulp webpack" or "gulp systemjs" without the quotes), it will actually run through more of the tasks than specified in my desired task.
I won't list all the tasks I've got within this for brevity, but they all follow the standard approach, as in the following sample:
gulp.task("angular",
() => {
var angularDirs = "./Scripts/MyApp/src/**/*.{html,css}";
return gulp.src(angularDirs)
.pipe(copy(config.wwwroot, { prefix: 1 }))
.pipe(gulp.dest(config.wwwroot));
});
For example, here's what I've got for my webpack task:
gulp.task("webpack", runSequence(["cleanRoot", "cleanBuild"],
["ts:webpack", "restore", "less", "angular", "webpackHtml", "javascript:webpack"]));
...and here's what I've got in the systemjs task:
gulp.task("systemjs", runSequence(["cleanRoot", "cleanBuild"], "embedTemplates",
"ts:systemjs", ["less", "restore", "angular"], "cleanWrongIndex"));
So, there's some overlap in there, but that's intended. However, if I run "gulp systemjs", I would expect that it'll only actually run "cleanRoot" and "cleanBuild" together, then "embedTemplates", then "ts:systemjs", the "less", "restore" and "angular" tasks and finally "cleanWrongIndex" and none of the other tasks in the file. However...
PS C:\Code\MyApp> gulp systemjs
[22:56:59] Using gulpfile
[22:56:59] Starting 'systemjs'...
[22:56:59] Finished 'systemjs' after 128 μs
[22:57:00] Finished 'cleanBuild' after 1.12 s
[22:57:01] Starting 'embedTemplates'...
**[22:57:01] Starting 'ts:webpack'...**
[22:57:01] Starting 'restore'...
[22:57:01] Starting 'less'...
[22:57:01] Starting 'angular'...
**[22:57:01] Starting 'webpackHtml'...**
**[22:57:01] Finished 'webpackHtml' after 705 μs**
**[22:57:01] Starting 'javascript:webpack'...**
**[22:57:01] Finished 'javascript:webpack' after 1.5 ms**
[22:57:01] Finished 'cleanRoot' after 1.9 s
[22:57:01] Finished 'restore' after 68 ms
[22:57:06] Finished 'less' after 5.65 s
[22:57:07] Finished 'angular' after 6.26 s
**[22:57:13] Finished 'ts:webpack' after 12 s**
**[22:57:14] Starting 'ts:systemjs'...**
[22:57:14] Finished 'embedTemplates' after 13 s
[22:57:20] Starting 'less'....
[22:57:20] Starting 'restore'...
[22:57:20] Starting 'angular'...
**[22:57:20] Finished 'ts:systemjs' after 5.64 s**
[22:57:20] Finished 'restore' after 161 ms
[22:57:23] Finished 'less' after 3.32 s
[22:57:23] Finished 'angular' after 3.79 s
[22:57:38] Starting 'restore'...
[22:57:38] Starting 'cleanWrongIndex'...
[22:57:38] Finished 'restore' after 25 μs
[22:57:38] Finished 'cleanWrongIndex' after 4.97 ms
PS C:\Code\MyApp>
I differentiated the tasks in the above that shouldn't be there since they're in the webpack task and not specified in this one.
Why are tasks showing up that I didn't specify? Is there any way to force gulp to only run the tasks I specify?
Thanks!
I am attempting to run a Gulp task and I get an error that I have no idea how to fix or even debug. The Gulp file and tasks have been created by NetSuite and haven't been editted by myself (they should work out of the box).
Any idea what node package could be causing the following error and how I can fix the error? Maybe I need to use a different version of SASS or Font-Awesome?
C:\Users\MyUser\SuiteCommerce Advanced Mont Blanc>gulp local
[08:48:45] Warning: gulp version mismatch:
[08:48:45] Global gulp is 3.9.1
[08:48:45] Local gulp is 3.8.7
[08:48:53] Using gulpfile ~\SuiteCommerce Advanced Mont Blanc\gulpfile.js
(node:1372) DeprecationWarning: 'GLOBAL' is deprecated, use 'global'
[08:48:53] Starting 'local-install'...
[08:48:53] Finished 'local-install' after 79 μs
[08:48:53] Starting 'templates'...
[08:48:53] Starting 'macros-jst'...
[08:48:53] Finished 'macros-jst' after 242 μs
[08:48:53] Starting 'macros'...
[08:48:53] Starting 'javascript-entrypoints'...
[08:48:53] Finished 'javascript-entrypoints' after 13 ms
[08:48:53] Starting 'javascript-move'...
[08:48:53] Starting 'copy'...
[08:48:53] Starting 'less'...
[08:48:53] Finished 'less' after 364 μs
[08:48:53] Starting 'sass-prepare'...
[08:48:53] Starting 'languages'...
[08:48:53] Starting 'images'...
[08:48:53] Starting 'fonts'...
[08:48:53] Finished 'fonts' after 386 μs
[08:48:53] Starting 'watch-templates'...
[08:48:53] Finished 'watch-templates' after 335 ms
[08:48:53] Starting 'watch-macros'...
[08:48:53] Finished 'watch-macros' after 610 μs
[08:48:53] Starting 'watch-javascript'...
[08:48:54] Finished 'watch-javascript' after 580 ms
[08:48:54] Starting 'watch-less'...
[08:48:54] Finished 'watch-less' after 459 μs
[08:48:54] Starting 'watch-sass'...
[08:48:55] Finished 'watch-sass' after 1.5 s
[08:48:55] Starting 'watch-languages'...
[08:48:55] Finished 'watch-languages' after 88 ms
[08:48:55] Starting 'watch-fonts'...
[08:48:56] Finished 'watch-fonts' after 365 μs
[08:48:56] Starting 'watch-images'...
[08:48:56] Finished 'watch-images' after 41 ms
[08:48:56] Finished 'copy' after 2.63 s
[08:48:56] Finished 'macros' after 2.71 s
[08:48:57] Finished 'javascript-move' after 4.15 s
[08:49:02] Finished 'images' after 9.11 s
[08:49:06] Finished 'languages' after 13 s
[08:49:07] Finished 'templates' after 14 s
[08:49:07] Starting 'javascript'...
[08:49:12] Finished 'sass-prepare' after 19 s
[08:49:12] Starting 'generate-sass-index'...
[08:49:12] Finished 'generate-sass-index' after 118 ms
[08:49:12] Starting 'sass'...
[08:49:12] Finished 'javascript' after 4.99 s
[08:49:12] Starting 'clean-templates'...
[08:49:12] Finished 'clean-templates' after 12 μs
[08:49:13] SOURCE CODE ERROR
[08:49:13] status 1
[08:49:13] file C:/Users/MyUser/SuiteCommerce Advanced Mont Blanc/LocalDistribution/sass/twitter-bootstrap-sass/mixins/_grid-framework.scss
[08:49:13] line 11
[08:49:13] column 245
[08:49:13] message LocalDistribution\sass\twitter-bootstrap-sass\mixins\_grid-framework.scss
Error: You may not #extend an outer selector from within #media.
You may only #extend selectors within the same directive.
From "#extend .col-md-6" on line 134 of LocalDistribution/sass/ItemDetails/_item-details.scss
on line 11 of LocalDistribution/sass/twitter-bootstrap-sass/mixins/_grid-framework.scss
>>
[08:49:13] formatted Error: You may not #extend an outer selector from within #media.
You may only #extend selectors within the same directive.
From "#extend .col-md-6" on line 134 of LocalDistribution/sass/ItemDetails/_item-details.scss
on line 11 of LocalDistribution/sass/twitter-bootstrap-sass/mixins/_grid-framework.scss
>>
[08:49:13] messageFormatted LocalDistribution\sass\twitter-bootstrap-sass\mixins\_grid-framework.scss
Error: You may not #extend an outer selector from within #media.
You may only #extend selectors within the same directive.
From "#extend .col-md-6" on line 134 of LocalDistribution/sass/ItemDetails/_item-details.scss
on line 11 of LocalDistribution/sass/twitter-bootstrap-sass/mixins/_grid-framework.scss
>>
[08:49:13] name Error
[08:49:13] stack Error: LocalDistribution\sass\twitter-bootstrap-sass\mixins\_grid-framework.scss
Error: You may not #extend an outer selector from within #media.
You may only #extend selectors within the same directive.
From "#extend .col-md-6" on line 134 of LocalDistribution/sass/ItemDetails/_item-details.scss
on line 11 of LocalDistribution/sass/twitter-bootstrap-sass/mixins/_grid-framework.scss
>>
at options.error (C:\Users\MyUser\SuiteCommerce Advanced Mont Blanc\node_modules\node-sass\lib\index.js:286:26)
[08:49:13] showStack false
[08:49:13] showProperties true
[08:49:13] plugin gulp-sass
[08:49:13] Finished 'sass' after 954 ms
[08:49:13] Starting 'font-awesome'...
[08:49:13] Starting 'clean-sass-tmp'...
[08:49:13] Finished 'clean-sass-tmp' after 5.57 μs
events.js:160
throw er; // Unhandled 'error' event
^
Error: Checksum error in glyf
It looks like you have node > v4 installed.
If you haven't run npm install since updating node you'll need to do that so SASS get's a new executable.
Running npm install may fix your issue
then gulp clean and gulp local.
Due to how often I see errors just running gulp local I generally run these as a single command:
gulp clean && gulp local
However I also go through and fix all those issues in the Netsuite's SASS files. Almost all of them are due to overspecification and I haven't seen any issues caused by fixing them.
e.g. From NS
.item-details-main {
#media (min-width: $screen-md-min) {
#extend .col-md-4;
}
}
behaves pretty much the same as:
.item-details-main {
#extend .col-md-4;
}
This error happens because SCA uses gulp-sass for compiling SCSS files. After Mont Blanc was released, node-sass, which is a dependency of gulp-sass was updated causing errors with SCSS files that were previously compiled.
There is no a fix for this issue without modifying SCSS files which throw fatal errors, but there is a workaround:
Uninstalling the gulp-sass package
Installing node-sass at 3.4.1 as a first-level dependency of the dev tools.
Reinstalling gulp-sass
In order to do this, run the following commands:
npm cache clear
npm uninstall gulp-sass node-sass
npm config set save-exact true
npm install --save node-sass#3.4.1 gulp-sass#2.1.0
I'm creating a site with yeoman using the yeogurt generator. After running yo yeogurt and going through the options, it finishes successfully with no errors and tells me I should now run gulp serve. However, when I do, it gets stuck on the last line of the output below:
[16:08:16] Using gulpfile ~/myproj/gulpfile.js
[16:08:16] Starting 'imagemin'...
[16:08:16] Starting 'copy'...
[16:08:16] Starting 'jade'...
[16:08:16] Starting 'sass'...
[16:08:16] Finished 'sass' after 124 ms
[16:08:16] Starting 'browserify'...
[16:08:16] Starting 'browserSync'...
[16:08:16] Finished 'browserSync' after 9.69 ms
[16:08:16] Starting 'watch'...
[16:08:16] Finished 'watch' after 39 ms
[16:08:16] gulp-imagemin: Minified 0 images
[16:08:16] Finished 'imagemin' after 355 ms
[BS] Access URLs:
-----------------------------------------
Local: http://localhost:3000/./
External: http://192.168.1.115:3000/./
-----------------------------------------
UI: http://localhost:3001
UI External: http://192.168.1.115:3001
-----------------------------------------
[BS] Serving files from: tmp
[BS] Reloading Browsers...
[16:08:16] Finished 'jade' after 492 ms
[16:08:16] Finished 'copy' after 495 ms
[BS] 1 file changed (main.css)
[16:08:17] 715847 bytes written (0.71 seconds)
./src/_scripts/main.js was browserified: 0.754s
[BS] Reloading files that match: *.js
I'm having a hard time tracking down this error.
For posterity: it wasn't 'stuck' at all. It had run successfully and the server was active on port 3000. I was just used to Gulp opening the browser window for you when the server starts, but with Yeogurt, it doesn't do that unless you add the --open flag.