-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 for Angular 16.x #2163
Comments
the ngx-table isn't working with angular 16.2.0 in style.scss
it produces this error:
|
Workaround: Put the styles path directly to node_modules in global.scss: |
I'm getting this error with Material 16 and Angular 16, any work around for this ? My Package.json
|
This didn't work for me |
I had the same error after upgrading to Angular 16 I my case, the problem was the angular modules that I imported from other external packages. Go trough app.module.ts to all imported modules you use, and check if there is an error within those files. If so, try to upgrade all the external modules you use. This error has nothing to do with the ngx-datatable, but rather other modules you import which makes all the modules broken and thus the ngx-datatable could not be resolved. |
Maybe too obvious, but to ensure the correct import of the .scss file, it's important to understand the relative paths in your project's directory structure: If your style.scss file is located in the src directory, you should use the following import statement:
In this case, ../ signifies moving up one directory level to reach the project's root, and then navigating to the desired node_modules directory. However, if your scss file is located in a deeper folder, such as src/css, you'll need to adjust the import statement accordingly. Here's how it should look:
In this example, we've used ../../ to move up two directory levels to reach the project's root, and then proceeded to the node_modules directory. |
I'm submitting a ... (check one with "x")
Current behavior
Expected behavior
Reproduction of the problem
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Table version:
Angular version:
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
The text was updated successfully, but these errors were encountered: