sencha/ext-allshared

ext-allshared

ext-allshared's Issues

ext-webpack-plugin swallows underlying errors

Not sure when this change occurred, but when using the ExtWebpackPlugin, any error that occurs after processing of the plugin itself, the underlying error is swallowed and the user has no visibility into the problem.

Simple way to replicate this:

1. Launch anything on port 8080 for example (e.g. make sure the port is in use)
2. Launch webpack w/ this plugin, and use port 8080... the process will start and then die and give you NO indication as to what hte problem is...

Offending code is somewhere in this block

ext-allshared/packages/ext-webpack-plugin/src/index.js

Lines 22 to 37 in 3afcf36

	var v = [`exit`, `SIGINT`, `SIGUSR1`, `SIGUSR2`, `uncaughtException`, `SIGTERM`]
	v.forEach(eventType => {
	process.on(eventType, function(eventType){
	if (me.vars.child != null) {
	console.log('\nnode process and sencha cmd process ended')
	me.vars.child.kill();
	me.vars.child = null;
	}
	else {
	if (eventType != 0) {
	console.log('\nnode process ended')
	}
	}
	process.exit();
	});
	})

please fix this! We lose countless hours troubleshooting by trial and error since we cant see the underlying problems when performing other webpack configurations.

With the plugin swallowing anything, this is a sample of all you see with vebose enabled:

XXXXXXXX@XXXXXXXX MINGW64 /d/src/XXXXXXX (feature-21377-webpack)
$ npm run watch

> [email protected] watch D:\src\XXXXXXX 
> webpack-dev-server --env.browser=no --env.verbose=yes --progress --color

-verbose: FUNCTION _constructor
-verbose: pluginName - ext-webpack-plugin
-verbose: app - i [ext]: 
i [ext]: ext-webpack-plugin v7.2.0, Ext JS v7.2.0 Commercial Edition, Sencha Cmd v7.2.0.84, webpack v4.39.3, react v16.12.0
i [ext]: Starting development build for react
-verbose: Building for development, treeshake is no, intellishake is yes
-verbose: FUNCTION _thisCompilation
-verbose: options.script:
-verbose: buildstep: 1 of 1
-verbose: FUNCTION _compilation
10% building 1/1 modules 0 active
node process ended

Unable to access ExtJS 7.5.0 sample application

I recently got myself into ExtJS. Followed the 'Getting started with NPM' and run a fresh modern-app sample. While the sample does seem to run, I noticed the following error.

i [ext]: [ERR] [ERR] Error: spawn /node_modules/@sencha/cmd/dist/sencha EACCES 
at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19) 
at onErrorNT (node:internal/child_process:477:16) 
at processTicksAndRejections (node:internal/process/task_queues:83:21)

My browser endlessly loading the app and this warning appeared on my console

<i> [webpack-dev-middleware] wait until bundle finished: /

I have tried to wait several minutes just in case of Webpack actually bundling assets but the same warning appeared.

ExtWebpackPlugin: Incorrectly assumes `index.html` in use

Using app.json, you can disable/change the page output path. Recent changes to ExtWebpackPlugin incorrectly assume that index.html is in use, and the process bombs if it is not...

Error: ENOENT: no such file or directory, lstat 'D:\XXX\clients\admin\build\production\index.html'
    at Object.fs.lstatSync (fs.js:941:11)
    at replacizeFileSync (D:\XXX\clients\admin\node_modules\replace\replace.js:140:22)
    at module.exports (D:\XXX\clients\admin\node_modules\replace\replace.js:80:17)
    at ExtWebpackPlugin.postBuildProcess (D:\XXX\clients\admin\node_modules\@sencha\ext-webpack-plugin\dist\index.js:114:9)
    at compiler.hooks.done.tap.stats (D:\XXX\clients\admin\node_modules\@sencha\ext-webpack-plugin\dist\index.js:88:12)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (D:\XXX\clients\admin\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:9:1)
    at AsyncSeriesHook.lazyCompileHook (D:\XXX\clients\admin\node_modules\tapable\lib\Hook.js:154:20)

app.json snippet

"output": {
    "base": "${workspace.build.dir}/${build.environment}",
    "page": {
      "path": "../../../../Views/Admin/Index.cshtml",
      "enable": false
    },
}

Sencha meta cmd with ext-webpack-plugin

Hi,

I would like to use ext-webpack-plugin in my project but I face to some troubles due to a wrong base path in the boostrap.js. According to the doc, I should be able to change that by using sencha meta command but I didn't find how to use that with the extjs webpack plugin.

Could you provide me some helps, please ?

Thanks