-
Notifications
You must be signed in to change notification settings - Fork 70
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
fix: babel loader and buildrc #1138
base: master
Are you sure you want to change the base?
Conversation
Hey @BalrokHS, first of all, thanks a lot for you contribution 🤗, however, the I'm not completely against merging this PR, but given that the tool is no longer maintained I wonder if it makes sense, because if it breaks anything, we will need to roll it back, as we (the owners of this project) are probably not going to fix it, which may lead to a series of merges and rollbacks until you or someone else from the community stabilizes it 😬. So, my proposal is that you first check if you can use In any case, let's first check if you can use |
The problem with Liferay/cli is that I can't seem to inject any of the ClayUI dependencies that are inside of the Liferay instance. Im using 7.4.3.75 through docker and Im getting the following error on dev:
Also on build. Could you guide me in order to resolve this with Liferay Remote App CLI implementation ? |
Strange. That should work as long as you use the correct target platform (see https://github.com/liferay/liferay-frontend-projects/blob/master/target-platforms/README.md) |
For example, the bundler import for classnames is defined in the Without having more information or a sample project it's difficult to tell what can be happening... |
Im downgrading to 7.4.3.75, and I will come back with the results. Question. In a remote app can I use a react router with a HashRouter ? |
@izaera After a long series of tries, I got it to work with Liferay/portal 7.4.3.55-ga55 on Docker. I imported the following dependencies: Also tried to build and succeeded. React router does not seem to have a problem. (Maybe I can post my results with a guide for the community. If you agree, please show me where 😆 ). A recommendation is to fix the documentation of Liferay portlet creation, since the top search lead to the deprecated way and can be really confusing. Great work with the Liferay-cli. In the case of the PR, I think it resolves some issues that exist, so in case you decide to continue to maintain this, feel free to review the changes and accept them or even change them 😄 |
@BalrokHS Great news! 🎉 Very happy that you made it work. Let me find out if there's some way for you to post a blog entry 👍 . Regarding the docs, are you referring to the ones in this project? The READMEs that I linked? And for the PR, I'll ask too what we can do. Thx. |
@pablo-agulla @dsanz what do you think about merging this PR? Should we try it, or should we reject it and recover this notice -> ec73c65 We used to redirect people from generator-liferay-js to liferay/cli in the past, but we had to remove the message because of the Workspace (see 0662139). Maybe it's time to recover the message (possibly hiding it when inside a workspace) and freeze this project correctly (including the README, which is a bit ambiguous). |
Hey @BalrokHS, the canonical place to create a blog post is https://liferay.dev/. You can create an account and post your findings there 👍 |
In the latest Liferay React generator, I faced the following issues, that I was able to reproduce on different OS and setups.
The issues are:
I added the first version, that I found it was compatible. Feel free to up/downgrade the version of babel-loader.