search

ardatan / meteor-webpack

https://medium.com/@ardatan/meteor-with-webpack-in-2018-faster-compilation-better-source-handling-benefit-from-bc5ccc5735ef
MIT License
123 stars 29 forks source link

Has anyone dealt with nested imports? #28

Closed jolim24601 closed 6 years ago

jolim24601 commented 6 years ago

Working on migrating a meteor 1.7 app to use webpack but I keep getting the nested imports error. Has anyone dealt with this and if so what did you do? Most of the imports are wrapped in Meteor.isServer blocks.

ardatan commented 6 years ago

meteor-webpack compiles client and server codes seperately. That's why, I recommend you to use seperate endpoints for your client and server code instead of seperating your codes with Meteor.isServer, because the blocks in Meteor.isServer condition will be compiled for client as well; so this is error prone. I'm closing this issue, you can open a new one with some detailed information like stack trace, your environment, reproduction etc.

jolim24601 commented 6 years ago

Thanks for replying @ardatan . This isn't really a bug however, I was asking for technical advice as I'm dealing with a fairly large codebase. Separating client from server code would be a huge task so I was wondering if anyone has dealt with this issue before. I was thinking potentially of using the reify babel plugin and then using reify on client and server at runtime, essentially this would mirror what meteor does. I was wondering if there were other options besides this. Thanks for your work.