Closed binsarjr closed 1 year ago
The introduction of loading GPU.js that way was so that the browser version worked correctly. Does simply removing it fix everything?
The introduction of loading GPU.js that way was so that the browser version worked correctly. Does simply removing it fix everything?
for nodejs library yes. the problem is gpu.js as a peerDepedency. so, when user downlaoded gpu.js, it will create for user node_modules path not our pacakge. it make wrong path when we use require('brain.js')
but for browser rollup it will be needed.
fix #885
Description
fix eror cannot find module. that error because when bran.js set gpu.js as peer dependecies. its not installed in our path. but,in user
Motivation and Context
issue
How Has This Been Tested?
i only change external rollup setting
Screenshots (if appropriate):
Types of changes
Author's Checklist:
Reviewer's Checklist: