Uncaught TypeError: Cannot read property '0' of undefined at Object.require.624../cjs/react-is.development.js
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 30/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- javascript, react
- Área
- build-system, tooling
Línea de trabajo
Comienza con el script de Browserify y sus salidas de factor-bundle; después reproduce el fallo usando el import de recharts y el bundle a.js generado. Compara los factor bundles generados con un bundle normal de Browserify e inspecciona la sección de react-is alrededor de arguments[4][722][0]; se considera terminado cuando el bundle dividido se carga sin el TypeError.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I have some React components that I am bundling with browserify, and I decided to try out factor-bundle to split code between pages of my app. Here is the js file I have written to browserify with factor-bundle:
var browserify = require('browserify');
var fs = require('fs');
var pwd = './usr/local/www/documents/media/js/react/'
var dest = './usr/local/www/documents/media/js/browserified/'
var files = [ pwd + 'a.js', pwd + 'b.js' ];
var b = browserify(files);
b.plugin('factor-bundle', {
outputs: [ dest + 'a.js', dest + 'b.js']
});
b.bundle().pipe(fs.createWriteStream(dest + 'common.js'));
When importing that newly created a.js bundle into an HTML doc, I get the following error that crashes the React component:
Uncaught TypeError: Cannot read property '0' of undefined
at Object.require.624../cjs/react-is.development.js (eval at globalEval (jquery.min.js:2), <anonymous>:57741:18)
at s (eval at globalEval (jquery.min.js:2), <anonymous>:1:262)
at eval (eval at globalEval (jquery.min.js:2), <anonymous>:1:313)
at Object.require.615../DataUtils (eval at globalEval (jquery.min.js:2), <anonymous>:57426:16)
at s (eval at globalEval (jquery.min.js:2), <anonymous>:1:262)
at eval (eval at globalEval (jquery.min.js:2), <anonymous>:1:313)
at Object.require.579.../util/DataUtils (eval at globalEval (jquery.min.js:2), <anonymous>:52263:19)
at s (eval at globalEval (jquery.min.js:2), <anonymous>:1:262)
at eval (eval at globalEval (jquery.min.js:2), <anonymous>:1:313)
at Object.require.587../cartesian/Area (eval at globalEval (jquery.min.js:2), <anonymous>:37928:14)
The error is not very informative, but by removing some lines of code, I was able to find that the presence of the following line was causing the issue to appear:
import {Area, AreaChart, XAxis, YAxis, CartesianGrid, Tooltip, Legend, ResponsiveContainer} from "recharts";
I am not sure to think that this issue has anything to do with recharts. If I browserify all my react code into a single bundle, I am able to import and use that bundle just fine. But if I import a.js with factor-bundle, this issue will appear.
Using the links given by the console log's error, the line that is failing looks something like this:
exports.parseChildIndex = parseChildIndex;
},{"./DataUtils":821,"./ShallowEqual":829,"lodash/flatten":650,"lodash/get":651,"lodash/isArray":656,"lodash/isNil":665,"lodash/isString":671,"react":757,"react-is":837}],837:[function(require,module,exports){
arguments[4][722][0].apply(exports,arguments)
},{"./cjs/react-is.development.js":835,"./cjs/react-is.production.min.js":836,"_process":710,"dup":722}],836:[function(require,module,exports){
....
Where the bolded [0] is what is marked as the breaking code. Not sure how or why this is happening, but using normal browserify does not cause this issue, which makes me think it has more to do with what's going on in factor-bundle than the recharts package.
I know this is an obscure issue. Any help would be appreciated because code-splitting would be very helpful for my app.
- Lenguaje dominante
- JavaScript
- Estrellas
- 397
- Forks
- 24
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de browserify/factor-bundle
-
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
browserify/factor-bundle#95 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
browserify/factor-bundle#92 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
browserify/factor-bundle#83 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
browserify/factor-bundle#82 · 3 reacciones ·
-
Module not found but still works Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
browserify/factor-bundle#81 · 2 comentarios ·
Todos los issues de browserify/factor-bundle
Issues similares
-
Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Automattic/safe-publish#594 ·
-
内部文件键(绝对路径的 base64)泄漏到界面标签 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
dream-num/dsh-univer-office#104 ·
-
comp/dashboard invalid P3
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
NousResearch/hermes-agent#121143 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
avniproject/avni-webapp#1811 ·
-
area/auroraboot area/webui bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100