Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ATTENTION: The "eval" devtool has been used (0.1.5 npm) #50

Open
Bonnev opened this issue Sep 22, 2022 · 0 comments
Open

ATTENTION: The "eval" devtool has been used (0.1.5 npm) #50

Bonnev opened this issue Sep 22, 2022 · 0 comments

Comments

@Bonnev
Copy link

Bonnev commented Sep 22, 2022

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant