-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support NativeScript 8 #77
Comments
The const webpack = require("@nativescript/webpack");
module.exports = (env) => {
webpack.init(env);
return webpack.resolveConfig();
}; Just make sure to have Everything else is handled internally inside This is an "internal" implementation detail - meaning that if we need to make adjustments we should do them there. User-end adjustments may be done in the We have updated the template to use ns8 & webpack5 - https://github.com/NativeScript/nativescript-app-templates/tree/master/packages/template-blank-react you can use that to test your changes (removal of bottom-nav, tabs etc.). |
I see, so the user inherits that React config and can make additional changes if they wish. I'll use your provided code snippet. (It runs!) Something's indeed up with HMR, though (as you've mentioned). I'll take some notes of what I've seen:
Apart from there being far more lines of logs spewed out than there were back when HMR was working, this What's really curious is that we didn't see the message react-nativescript/react-nativescript/src/index.ts Lines 259 to 276 in 6f1d8ec
This implies that the calls for the NativeScript Core Application APIs |
It is possible to support NS8 in RNS, It seems to sad to say all framework are current support NS8 except RNS. |
@HakobiDev I’m using this issue broadly to track regressions since Webpack 4 & NS7, but NS8 itself is supported. Use the latest starter template with HMR support will come later. Tabs and BottomNavigation are implemented and will be supported when the next release of Material Components comes out, but TabView can be used as a substitute for now. |
I've so far updated RNS itself to support NativeScript v8 (that's
[email protected]
for anyone interested), but it means nothing until I've also updated the RNS Webpack config to support Webpack v5. After that, I'll need to make React plugins for Tabs and BottomNavigation and update RNS Navigation correspondingly. Finally, I'll need to update the RNS app template. I may need to update the RNS docs, too.The immediate hurdle is the Webpack config.
@rigor789 I'm getting this error when supplying this webpack.config.js which is just the JS equivalent of your configuration.react.ts:
I also looks like the Webpack API has possibly changed from
webpack.init(env)
toconfigs.base(config, env)
since you wrote the docs.The text was updated successfully, but these errors were encountered: