You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the published version 0.1.5 (link to build) contains eval()s which is not a good thing to use beyond development. The beginning shows a clear warning:
/*
* ATTENTION: The "eval" devtool has been used (maybe by default in mode: "development").
* This devtool is neither made for production nor for readable output files.
* It uses "eval()" calls to create a separate source file in the browser devtools.
* If you are trying to read the output file, select a different devtool (https://webpack.js.org/configuration/devtool/)
* or disable the default devtool with "devtool: false".
* If you are looking for production-ready output files, see mode: "production" (https://webpack.js.org/configuration/mode/).
*/
This is not the case for the earlier 0.1.4 version (link)
I see that anyways a new version 0.1.6 is ready, containing also TypeScript. Could you publish that version and this time not use eval?
The text was updated successfully, but these errors were encountered:
It seems like the published version 0.1.5 (link to build) contains
eval()
s which is not a good thing to use beyond development. The beginning shows a clear warning:This is not the case for the earlier 0.1.4 version (link)
I see that anyways a new version 0.1.6 is ready, containing also TypeScript. Could you publish that version and this time not use eval?
The text was updated successfully, but these errors were encountered: