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
Probably using the different configs per environment, we should allow some modules to not be loaded by MeanIO. This could be helpful for special logging packages, or debugging packages.
The text was updated successfully, but these errors were encountered:
Part of this request (feature flags, or toggling code by env) could be hacked around now by setting globals with webpack and DefinePlugin, but it means wrapping every file in the package in an if statement, and only works on public/frontend files. Also will still process import statements at the top of files (afaik you are not allowed to do conditional imports by design of the import API), so really only works if using require/require.ensure
new webpack.DefinePlugin({
'process.env':{
'NODE_ENV': JSON.stringify(process.env.NODE_ENV),
}
})
if (process.env.NODE_ENV === 'production) {
angular code here
}
Probably using the different configs per environment, we should allow some modules to not be loaded by MeanIO. This could be helpful for special logging packages, or debugging packages.
The text was updated successfully, but these errors were encountered: