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
Hello, I created an app using this command
yarn create r3f-app next my-app styled -ts
Then in the index page it says that if i click de box it should go to the box page, but it doesnt. Also the events like onPointerOver and onPointerOut are not getting called.
Finally when I start the app in development mode it display this warning on the vscode terminal.
(node:16492) [DEP_WEBPACK_SINGLE_ENTRY_PLUGIN] DeprecationWarning: SingleEntryPlugin was renamed to EntryPlugin (Use "node --trace-deprecation ..." to show where the warning was created) Defining routes from exportPathMap (node:16492) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated. BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation. Do changes to assets earlier, e. g. in Compilation.hooks.processAssets. Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
The text was updated successfully, but these errors were encountered:
Hello, I created an app using this command
yarn create r3f-app next my-app styled -ts
Then in the index page it says that if i click de box it should go to the box page, but it doesnt. Also the events like onPointerOver and onPointerOut are not getting called.
Finally when I start the app in development mode it display this warning on the vscode terminal.
(node:16492) [DEP_WEBPACK_SINGLE_ENTRY_PLUGIN] DeprecationWarning: SingleEntryPlugin was renamed to EntryPlugin (Use "node --trace-deprecation ..." to show where the warning was created) Defining routes from exportPathMap (node:16492) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated. BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation. Do changes to assets earlier, e. g. in Compilation.hooks.processAssets. Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
The text was updated successfully, but these errors were encountered: