In the build kit, I see a network request for: systemjs-plugin-babel@0.0.21.json from the cache ... in the same instance, where it cannot fully load the entire path to my application.
Unable to load anything redirected from http: // thehost / myapp / jspm_packages / npm
I understand that in the combined JSPM module, it should never be loaded from this route, since everything is inserted into the build.js file.
I am currently associating my application with the following gulp task:
gulp.task('jspm-bundle', plugins.shell.task([ 'node node_modules/jspm/jspm.js bundle myapp/index.jsx' + ' + myapp/things/**/*.jsx + myapp/otherthings/**/*.jsx' + ' + systemjs-plugin-babel + babel-preset-stage-0 + transform-react-jsx' + ' + transform-decorators-legacy' + ' --minify --skip-source-maps' ])
I'm not sure where to start ... can someone tell me a few reasons why the embedded application will even try to make such a request in the browser?
Update 1:
At some point, we saw a rejection of the promise, which was also associated with this only client:
Unhandled promise rejection Error: Syntax Error Instantiating http://myhost/myapp/jspm_packages/npm/ systemjs-plugin-babel@0.0.21.json Loading http://myhost/myapp/jspm_packages/npm/ systemjs-plugin-babel@0.0.21.json Unable to fetch package configuration file http://myhost/myapp/jspm_packages/npm/ systemjs-plugin-babel@0.0.21.json Resolving plugin-babel to http://myhost/myapp/app/index.jsx Resolving myapp/index.jsx Loading myapp/index.jsx
Update 2:
My FULL SystemJS config: https://pastebin.com/aJFPqNGn
Update 3 (last update?):
I can recreate the production problem if I explicitly import from "npm: systemjs-plugin-babel", but I cannot explain why this import will occur during production on a client installation. A syntax error occurs because a request for a nonexistent file returns an input html and a syntax error occurs when the first '<' in html
source share