Skip to content
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

Remove Lombiq.NodeJs.Extensions #538

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

Remove Lombiq.NodeJs.Extensions #538

wants to merge 7 commits into from

Conversation

Skrypt
Copy link
Contributor

@Skrypt Skrypt commented Mar 11, 2025

Feel free to comment.

Fixes #527
Fixes #535

Copy link
Contributor

@sarahelsaig sarahelsaig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just removing the tool will break OCC, which is why tests are failing. As discussed in the issue, the JS files have to be moved (as indicated here, here and here). Also SCSS have to be ported to CSS (as indicated here and here)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If Lombiq.NodeJs.Extensions is removed, the package.json files won't be needed at all.

@Skrypt
Copy link
Contributor Author

Skrypt commented Mar 11, 2025

Thanks, I'll try doing that later this week.
I'm going to try also the multi-targetting of frameworks on a different PR.
I generally just copy the folder structure of OC and import the build files in my Nuget package solution. This was I spend less time changing that code on every releases.

@sarahelsaig
Copy link
Contributor

Thanks, I'll try doing that later this week.
I'm going to try also the multi-targetting of frameworks on a different PR.

That sounds good, much appreciated! 😊

Copy link

This pull request has merge conflicts. Please resolve those before requesting a review.

@Skrypt
Copy link
Contributor Author

Skrypt commented Mar 28, 2025

I've cleaned up the solution so that I could get multi-targeting working. Right now, it works but with a lot of errors to fix before being able to compile but I think I figured out most of the configs for multi-targeting.

@Skrypt
Copy link
Contributor Author

Skrypt commented Mar 28, 2025

I did change the structure of the folders so that it matches OC repository so that it be easier for me to just copy/paste some of the files that are in that repository. Normally, what I do is that I keep the same folder structure so that it is easier to just copy/paste configs/tools from OC to my Nuget package solutions. This way I don't need to change paths in these files.

Copy link
Contributor

@sarahelsaig sarahelsaig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The GitHub Actions build fails with a bunch of errors like this:

Error: /usr/share/dotnet/sdk/8.0.301/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.TargetFrameworkInference.targets(166,5): error NETSDK1045: The current .NET SDK does not support targeting .NET 9.0. Either target .NET 8.0 or lower, or use a version of the .NET SDK that supports .NET 9.0. Download the .NET SDK from https://aka.ms/dotnet/download [/home/runner/work/OrchardCore.Commerce/OrchardCore.Commerce/src/OrchardCore.Modules/OrchardCore.Commerce.Tax/OrchardCore.Commerce.Tax.csproj::TargetFramework=net9.0]

@Skrypt
Copy link
Contributor Author

Skrypt commented Mar 28, 2025

Yeah don't look too much at errors it's a WIP. Just letting you know to see if you agree with the folder structure change.

Copy link

This pull request has merge conflicts. Please resolve those before requesting a review.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume this whole App_Data directory was committed by accident?

You've changed the OrchardCore.Commerce.Web to OrchardCore.Cms.Web (why?) but then didn't update the .gitignore file, which is probably the reason.

@sarahelsaig
Copy link
Contributor

Yeah don't look too much at errors it's a WIP. Just letting you know to see if you agree with the folder structure change.

I see, thanks for the clarification. I am swamped now but I can look it over more on Monday.

@Piedone , do you have opinions about the folder structure change here? (or about nowarn stuff added to Directory.Build.props)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Multi-target builds (OCC-322) Consider removing node.js dependency (OCC-314)
2 participants