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
Running npm start on master produces an error: "module is not defined".
Steps to Reproduce
Run npm start
Expected Behavior
I started writing up this ticket because I thought this broke the test dashboard. However, it appears this console error is simply erroneous.
Actual Behavior
The test dashboard actually does not appear to break, despite the console error.
Additional Details
The CommonJS export syntax in //devtools/test_dashboard/devtools.js is at fault. It appears that ESBuild does not strip this out on build. To fix this, we could:
Remove the module.exports = Tabs line if this export is not needed elsewhere.
Create another file (e.g. index.js), import the devtools from there const Tabs = require('./tabs');, and point ESBuild at that.
The text was updated successfully, but these errors were encountered:
samhinshaw
changed the title
Developer Script Produces Errornpm start Produces Error
Dec 11, 2024
Running
npm start
onmaster
produces an error: "module is not defined".Steps to Reproduce
npm start
Expected Behavior
I started writing up this ticket because I thought this broke the test dashboard. However, it appears this console error is simply erroneous.
Actual Behavior
The test dashboard actually does not appear to break, despite the console error.
Additional Details
The CommonJS export syntax in
//devtools/test_dashboard/devtools.js
is at fault. It appears that ESBuild does not strip this out on build. To fix this, we could:module.exports = Tabs
line if this export is not needed elsewhere.index.js
), import the devtools from thereconst Tabs = require('./tabs');
, and point ESBuild at that.The text was updated successfully, but these errors were encountered: