javafx-jpa-crud | Projeto demonstração com as tecnologias JavaFX e | Object-Relational Mapping library
kandi X-RAY | javafx-jpa-crud Summary
Support
Quality
Security
License
Reuse
- Inicializaize components
- Build the input fields
- Build the default buttons
- Reset the form
- Inicializa the CSS components
- Build the fields
- Build a text field
- Create an image box
- Handle an action
- Executes the action
- Extracts the actual action
- Inicializa the component
- Build the bbox
- Build the fields for the genome
- Returns a list of Mercadoras objects for a given name
- Execute the transactional action
- Register an event listener
- Validate the given Mercatoria entity
- Initiate components
- Gets the menu bar
- Gets the buttons box
javafx-jpa-crud Key Features
javafx-jpa-crud Examples and Code Snippets
Trending Discussions on Utilities
Trending Discussions on Utilities
QUESTION
I've been upgrading my CRA project to TailwindCSS 3, but now CSS nesting no longer works. Upon starting the server, the console spits out:
(8:3) Nested CSS was detected, but CSS nesting has not been configured correctly.
Please enable a CSS nesting plugin *before* Tailwind in your configuration.
See how here: https://tailwindcss.com/docs/using-with-preprocessors#nesting
However, I don't see what must be done to correct this. I've tried setting up a plain CRA project with Tailwind (following this guide) just to make sure I have no conflicts, and still no success.
postcss.config.js:
module.exports = {
plugins: {
"tailwindcss/nesting": {},
tailwindcss: {},
autoprefixer: {},
},
};
As you can see, I have added the nesting plugin before Tailwind. It appears to me as if the plugin isn't being detected whatsoever. I've also tried replacing it with postcss-nesting
with same outcome.
Note: I've also tried using the array syntax with require('tailwind/nesting')
like the guide suggests.
Interestingly, removing all plugins from postcss.config.js (or using a require
that fails to resolve) still outputs the same error, implying that this file isn't needed to get Tailwind to load. Maybe I am missing something that causes the whole postcss.config.js file to not be loaded in the first place?
index.js:
import React from "react";
import ReactDOM from "react-dom";
import "./index.css";
ReactDOM.render(
aaa
bbb
,
document.getElementById("root")
);
index.css:
@tailwind base;
@tailwind components;
@tailwind utilities;
.a {
@apply text-blue-500;
.b {
@apply text-green-500;
}
}
package.json: (omitted things for brevity)
{
"name": "tailwindtest",
"dependencies": {
"react": "^17.0.2",
"react-dom": "^17.0.2",
"react-scripts": "5.0.0"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"devDependencies": {
"autoprefixer": "^10.4.2",
"postcss": "^8.4.5",
"tailwindcss": "^3.0.12"
}
}
ANSWER
Answered 2022-Feb-03 at 18:38This is mostly just bad news.
Create React App's Tailwind support means that they will detect tailwind.config.js
in the project and add tailwindcss
to their existing postcss
configuration. Source in CRA
The guide that Tailwind offers on their site creates a dummy postcss.config.js
- Making changes in this file does not change the actual postcss configuration. (misleading if anything)
This is a known issue currently - Github discussion on Tailwind support PR between Adam Wathan (Tailwind founder) and Ian Sutherland (CRA maintainer). But it does not seem like there is an intention to be fixed soon.
If you want to use nesting (or any PostCSS plugin really) is to eject from CRA using:
npm run eject
After ejecting you can find CRA's postcss configuration in config/webpack.config.js
- look for postcss-loader
. Editing the configuration there can enable any postcss features.
PS: Look out for postcss-preset-env
in the default configuration while enabling nesting. Tailwind requires you to edit configuration if this is present.
QUESTION
I'm attempting to create an apollo client
plugin for a Nuxt 3
application. It's currently throwing an error regarding a package called ts-invariant
:
file:///Users/[my name]/Repositories/[project]/node_modules/@apollo/client/utilities/globals/fix-graphql.js:1
import { remove } from "ts-invariant/process/index.js";
^^^^^^
SyntaxError: Named export 'remove' not found. The requested module 'ts-invariant/process/index.js' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from 'ts-invariant/process/index.js';
const { remove } = pkg;
at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
at async ModuleJob.run (node:internal/modules/esm/module_job:181:5)
at async Promise.all (index 0)
at async ESMLoader.import (node:internal/modules/esm/loader:281:24)
at async __instantiateModule__ (file:///Users/[my name]/Repositories/[project]/.nuxt/dist/server/server.mjs:4550:3)
[vite dev] Error loading external "/Users/[my name]/Repositories/[project]/node_modules/@apollo/client/core/index.js".
at file://./.nuxt/dist/server/server.mjs:3170:289
at async __instantiateModule__ (file://./.nuxt/dist/server/server.mjs:4550:3)
I feel like I know enough about this error to know it has something to do with how Nuxt 3 deals with ESM, but I can't be for certain.
Here's the nuxt plugin:
plugins/apollo-client.js
import { defineNuxtPlugin } from "#app"
import { ApolloClient, InMemoryCache } from "@apollo/client/core"
import { DefaultApolloClient } from "@vue/apollo-composable"
export default defineNuxtPlugin((nuxtApp) => {
const config = useRuntimeConfig()
const apolloClient = new ApolloClient({
uri: config.PUBLIC_API_ENDPOINT,
cache: new InMemoryCache(),
})
nuxtApp.vueApp.provide(DefaultApolloClient, apolloClient)
})
In a normal scenario, I might use the nuxt-apollo community module, but it is currently afk regarding a nuxt 3
port, so a plugin it is.
Here's some documentation I relied on for my plugin:
https://v4.apollo.vuejs.org/guide-composable/setup.html#vue-3
https://v3.nuxtjs.org/docs/directory-structure/plugins
ANSWER
Answered 2022-Jan-07 at 01:52Solved by including @apollo/client
and ts-invariant/process
into the nuxt build transpile like so:
// nuxt.config.js
// ...
build: {
postcss: {
postcssOptions: require('./postcss.config.js')
},
transpile: [
'@apollo/client',
'ts-invariant/process',
],
},
// ...
QUESTION
Very first try on Nuxt3 via Nuxt3 Starter
I wonder how can I use tailwindcss in Nuxt3 Starter manually.
(Not via @nuxtjs/tailwindcss , because it's for Nuxt2, and not work with Nuxt3.)
I created a blank Nuxt3 project by
npx degit "nuxt/starter#v3" my-nuxt3-project
then, I installed the tailwindcss manually
npm install -D tailwindcss@latest postcss@latest autoprefixer@latest
nuxt.config.ts
export default {
css: [
'~/assets/tailwind.css',
]
}
assets/tailwind.css
@tailwind base;
@tailwind components;
@tailwind utilities;
but I can only get the raw code but not the compiled css:
How can I use tailwindcss in Nuxt3?
Any help is greatly appreciated!
ANSWER
Answered 2021-Oct-04 at 04:17Maybe your problem is because you need a tailwindcss.config.js
.
For this, simply type in the console:
yarn run tailwindcss init
QUESTION
In a fresh Laravel 9 installation, the URL processing from Laravel Mix does not work anymore.
npm outputs the following:
✖ Mix
Compiled with some errors in 2.62s
ERROR in ./resources/css/app.css
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/css-loader/dist/cjs.js):
Error: Can't resolve './fonts/Inter-Regular.woff' in '/mnt/c/projects/test-project/resources/css'
at finishWithoutResolve (/mnt/c/projects/test-project/node_modules/enhanced-resolve/lib/Resolver.js:304:18)
at /mnt/c/projects/test-project/node_modules/enhanced-resolve/lib/Resolver.js:381:15
at /mnt/c/projects/test-project/node_modules/enhanced-resolve/lib/Resolver.js:430:5
at eval (eval at create (/mnt/c/projects/test-project/node_modules/tapable/lib/HookCodeFactory.js:33:10), :16:1)
at /mnt/c/projects/test-project/node_modules/enhanced-resolve/lib/Resolver.js:430:5
at eval (eval at create (/mnt/c/projects/test-project/node_modules/tapable/lib/HookCodeFactory.js:33:10), :27:1)
at /mnt/c/projects/test-project/node_modules/enhanced-resolve/lib/DescriptionFilePlugin.js:87:43
at /mnt/c/projects/test-project/node_modules/enhanced-resolve/lib/Resolver.js:430:5
at eval (eval at create (/mnt/c/projects/test-project/node_modules/tapable/lib/HookCodeFactory.js:33:10), :15:1)
at /mnt/c/projects/test-project/node_modules/enhanced-resolve/lib/Resolver.js:430:5
at processResult (/mnt/c/projects/test-project/node_modules/webpack/lib/NormalModule.js:753:19)
at /mnt/c/projects/test-project/node_modules/webpack/lib/NormalModule.js:855:5
at /mnt/c/projects/test-project/node_modules/loader-runner/lib/LoaderRunner.js:399:11
at /mnt/c/projects/test-project/node_modules/loader-runner/lib/LoaderRunner.js:251:18
at context.callback (/mnt/c/projects/test-project/node_modules/loader-runner/lib/LoaderRunner.js:124:13)
at Object.loader (/mnt/c/projects/test-project/node_modules/css-loader/dist/index.js:155:5)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)
webpack compiled with 2 errors
The font file is just one of many. My app.css looks like this:
@import 'tailwindcss/base';
@import 'tailwindcss/components';
@import 'tailwindcss/utilities';
@import 'primevue/resources/primevue.css';
@import 'primevue/resources/themes/lara-light-indigo/theme.css';
@import 'primeflex/primeflex.css';
@import 'primeicons/primeicons.css';
The package.json contains the following dependencies/versions:
"devDependencies": {
"@inertiajs/inertia": "^0.10.0",
"@inertiajs/inertia-vue3": "^0.5.1",
"@inertiajs/progress": "^0.2.6",
"@tailwindcss/forms": "^0.4.0",
"@vue/compiler-sfc": "^3.0.5",
"autoprefixer": "^10.2.4",
"axios": "^0.25",
"laravel-mix": "^6.0.6",
"lodash": "^4.17.19",
"postcss": "^8.2.13",
"postcss-import": "^14.0.1",
"tailwindcss": "^3.0.0",
"vue": "^3.0.5",
"vue-loader": "^16.1.2"
},
"dependencies": {
"primeflex": "^3.1.2",
"primeicons": "^5.0.0",
"primevue": "^3.11.1",
"vue-i18n": "^9.1.9"
}
The webpack.mix.js is default:
mix.js('resources/js/app.js', 'public/js')
.vue()
.postCss('resources/css/app.css', 'public/css', [
require('postcss-import'),
require('tailwindcss'),
require('autoprefixer'),
])
.webpackConfig(require('./webpack.config'));
Is there something I haven't seen?
ANSWER
Answered 2022-Feb-22 at 10:55Actually moving the css imports into resources/js/app.js
solves this problem. However, this results in the imported css to be included in the public/js/app.js
, not the public/css/app.css
.
QUESTION
I'm trying the create a 3D subscene with objects being labelled using Label objects in a 2D overlay. I've seen similar questions to mine on this subject, and they all point to using the Node.localToScene method on the node to be labelled in the 3D space. But this doesn't seem to work for my case. I've taken example code from the FXyz FloatingLabels example here:
The Label objects need to have their positions updated as the 3D scene in modified, which I've done but when I print out the coordinates returned by the Node.localToScene method, they're much too large to be within the application scene, and so the labels are never visible in the scene. I've written an example program that illustrates the issue, set up very similarly to the FXyz sample code but I've created an extra SubScene object to hold the 2D and 3D SubScene objects in order to plant them into a larger application window with slider controls. The 3D scene uses a perspective camera and shows a large sphere with coloured spheres along the x/y/z axes, and some extra little nubs on the surface for reference:
import javafx.application.Application;
import javafx.application.Platform;
import javafx.scene.Group;
import javafx.scene.Node;
import javafx.scene.PerspectiveCamera;
import javafx.scene.SubScene;
import javafx.scene.Scene;
import javafx.scene.SceneAntialiasing;
import javafx.scene.AmbientLight;
import javafx.scene.PointLight;
import javafx.scene.control.Label;
import javafx.scene.control.Slider;
import javafx.scene.control.ToolBar;
import javafx.scene.layout.GridPane;
import javafx.scene.layout.StackPane;
import javafx.scene.layout.Priority;
import javafx.scene.shape.Sphere;
import javafx.scene.paint.Color;
import javafx.scene.paint.PhongMaterial;
import javafx.scene.transform.Rotate;
import javafx.scene.transform.Translate;
import javafx.stage.Stage;
import javafx.geometry.Point3D;
import java.util.Map;
import java.util.HashMap;
public class LabelTest extends Application {
private Map nodeToLabelMap;
@Override
public void start (Stage stage) {
// Create main scene graph
var objects3d = new Group();
Rotate xRotate = new Rotate (0, 0, 0, 0, Rotate.X_AXIS);
Rotate yRotate = new Rotate (0, 0, 0, 0, Rotate.Y_AXIS);
objects3d.getTransforms().addAll (
xRotate,
yRotate
);
var root3d = new Group();
root3d.getChildren().add (objects3d);
var camera = new PerspectiveCamera (true);
camera.setTranslateZ (-25);
var scene3d = new SubScene (root3d, 500, 500, true, SceneAntialiasing.BALANCED);
scene3d.setFill (Color.rgb (20, 20, 80));
scene3d.setCamera (camera);
var sceneRoot = new Group (scene3d);
var objects2d = new Group();
sceneRoot.getChildren().add (objects2d);
var viewScene = new SubScene (sceneRoot, 500, 500);
scene3d.widthProperty().bind (viewScene.widthProperty());
scene3d.heightProperty().bind (viewScene.heightProperty());
// Add lights and objects
var ambient = new AmbientLight (Color.color (0.7, 0.7, 0.7));
var point = new PointLight (Color.color (0.3, 0.3, 0.3));
point.setTranslateX (-25);
point.setTranslateY (-25);
point.setTranslateZ (-50);
root3d.getChildren().addAll (ambient, point);
var globe = new Sphere (5);
globe.setMaterial (new PhongMaterial (Color.color (0.3, 0.3, 0.3)));
var xSphere = new Sphere (0.5);
xSphere.setMaterial (new PhongMaterial (Color.RED));
xSphere.setTranslateX (5);
var ySphere = new Sphere (0.5);
ySphere.setMaterial (new PhongMaterial (Color.GREEN));
ySphere.setTranslateY (5);
var zSphere = new Sphere (0.5);
zSphere.setMaterial (new PhongMaterial (Color.BLUE));
zSphere.setTranslateZ (5);
objects3d.getChildren().addAll (globe, xSphere, ySphere, zSphere);
var nubMaterial = new PhongMaterial (Color.color (0.2, 0.2, 0.2));
for (int i = 0; i < 200; i++) {
var nub = new Sphere (0.125);
nub.setMaterial (nubMaterial);
var phi = 2*Math.PI*Math.random();
var theta = Math.acos (2*Math.random() - 1);
var z = -5 * Math.sin (theta) * Math.cos (phi);
var x = 5 * Math.sin (theta) * Math.sin (phi);
var y = -5 * Math.cos (theta);
nub.setTranslateX (x);
nub.setTranslateY (y);
nub.setTranslateZ (z);
objects3d.getChildren().add (nub);
} // for
// Add labels
var xLabel = new Label ("X axis");
xLabel.setTextFill (Color.RED);
var yLabel = new Label ("Y axis");
yLabel.setTextFill (Color.GREEN);
var zLabel = new Label ("Z axis");
zLabel.setTextFill (Color.BLUE);
objects2d.getChildren().addAll (xLabel, yLabel, zLabel);
nodeToLabelMap = new HashMap<>();
nodeToLabelMap.put (xSphere, xLabel);
nodeToLabelMap.put (ySphere, yLabel);
nodeToLabelMap.put (zSphere, zLabel);
xRotate.angleProperty().addListener ((obs, oldVal, newVal) -> updateLabels());
yRotate.angleProperty().addListener ((obs, oldVal, newVal) -> updateLabels());
camera.translateZProperty().addListener ((obs, oldVal, newVal) -> updateLabels());
Platform.runLater (() -> updateLabels());
// Create main pane
var gridPane = new GridPane();
var stackPane = new StackPane (viewScene);
viewScene.heightProperty().bind (stackPane.heightProperty());
viewScene.widthProperty().bind (stackPane.widthProperty());
viewScene.setManaged (false);
gridPane.add (stackPane, 0, 0);
gridPane.setVgrow (stackPane, Priority.ALWAYS);
gridPane.setHgrow (stackPane, Priority.ALWAYS);
// Add controls
var xSlider = new Slider (-90, 90, 0);
xRotate.angleProperty().bind (xSlider.valueProperty());
var ySlider = new Slider (-180, 180, 0);
yRotate.angleProperty().bind (ySlider.valueProperty());
var zSlider = new Slider (-60, -25, -25);
camera.translateZProperty().bind (zSlider.valueProperty());
ToolBar toolbar = new ToolBar (
new Label ("X rotation:"),
xSlider,
new Label ("Y rotation:"),
ySlider,
new Label ("Z position:"),
zSlider
);
gridPane.add (toolbar, 0, 1);
// Start the show
stage.setTitle ("Label Test");
stage.setScene (new Scene (gridPane, 800, 600));
stage.show();
} // start
private void updateLabels () {
nodeToLabelMap.forEach ((node, label) -> {
var coord = node.localToScene (Point3D.ZERO, true);
System.out.println ("label = " + label.getText() + ", coord = " + coord);
label.getTransforms().setAll (new Translate(coord.getX(), coord.getY()));
});
} // updateLabels
public static void main (String[] args) {
launch (args);
} // main
} // LabelTest class
You can compile and run the LabelTest.java program using this script (I'm using JavaFX 14 and JDK 14.0.2 on a Mac):
#!/bin/sh
set -x
export PATH_TO_FX=javafx-sdk-14/lib
javac --module-path $PATH_TO_FX --add-modules javafx.controls LabelTest.java
if [ $? -ne 0 ] ; then
exit 1
fi
java -cp . --module-path $PATH_TO_FX --add-modules javafx.controls LabelTest
My test program output contains very large label coordinates that don't represent the position of the coloured axis spheres, for example:
label = Y axis, coord = Point3D [x = 17448.00808897467, y = 21535.846392310217, z = 0.0]
label = X axis, coord = Point3D [x = 26530.33870777918, y = 12453.515773505665, z = 0.0]
label = Z axis, coord = Point3D [x = 17448.008088974653, y = 12453.515773505665, z = 0.0]
My display looks like this:
where as it should look more like the example from FXyz with labels next to the axis spheres:
ANSWER
Answered 2022-Feb-02 at 12:28If you follow what has been done in the link you have posted you'll make it work.
For starters, there is one subScene, not two.
So I've removed these lines:
- var viewScene = new SubScene (new Group (scene3d), 500, 500);
- scene3d.widthProperty().bind (viewScene.widthProperty());
- scene3d.heightProperty().bind (viewScene.heightProperty());
and replaced these:
- var stackPane = new StackPane (viewScene);
- viewScene.heightProperty().bind (stackPane.heightProperty());
- viewScene.widthProperty().bind (stackPane.widthProperty());
- viewScene.setManaged (false);
+ var stackPane = new StackPane (sceneRoot);
+ scene3d.heightProperty().bind (stackPane.heightProperty());
+ scene3d.widthProperty().bind (stackPane.widthProperty());
That works fine now for me:
label = Z axis, coord = Point3D [x = 613.2085772621016, y = 286.33580935946725, z = 0.0]
label = X axis, coord = Point3D [x = 401.67010722785966, y = 219.90328164976754, z = 0.0]
label = Y axis, coord = Point3D [x = 400.0, y = 503.57735384935296, z = 0.0]
QUESTION
I am new to angular and was following the documentation to build a basic app.
Node - v14.7.3
npm - 7.22.0
Angular CLI: 12.2.4
OS: win32 x64
@angular-devkit/architect 0.1202.4
@angular-devkit/build-angular 12.2.4
@angular-devkit/core 12.2.4
@angular-devkit/schematics 12.2.4
@schematics/angular 12.2.4
rxjs 6.6.7
typescript 4.3.5
So far all I have done is
npm install @angular/cli
followed by ng new firstApp
and ng serve
Following is the error that I am receiving,
√ Browser application bundle generation complete.
Initial Chunk Files | Names | Size
runtime.js | runtime | 4.89 kB
main.js | main | 3.56 kB
polyfills.js | polyfills | 3.55 kB
styles.js | styles | 3.54 kB
| Initial Total | 15.54 kB
Build at: 2021-09-06T06:20:42.162Z - Hash: f81b11c218148f716cf3 - Time: 10951ms
../../../../#Development/Files/angularProjects/firstApp/src/main.ts - Error: Module build failed: Error: Cannot find module 'F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-angular\src\babel\webpack-loader.js'
Require stack:
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\ProgressPlugin.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-webpack\src\webpack\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-webpack\src\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-angular\src\dev-server\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\architect\node\node-modules-architect-host.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\architect\node\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\models\architect-command.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\commands\serve-impl.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\schematics\tools\export-ref.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\schematics\tools\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\utilities\json-schema.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\models\command-runner.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\lib\cli\index.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\lib\init.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\bin\ng
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:92:18)
at F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\ProgressPlugin.js:412:9
at Hook.eval [as call] (eval at create (F:\#Development\Files\angularProjects\firstApp\node_modules\tapable\lib\HookCodeFactory.js:19:10), :7:1)
at NormalModule.doBuild (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:768:24)
at NormalModule.build (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:920:15)
at F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\Compilation.js:1322:12
at NormalModule.needBuild (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:1192:32)
../../../../#Development/Files/angularProjects/firstApp/src/polyfills.ts - Error: Module build failed: Error: Cannot find module 'F:\#Development\Files\angularProjects\firstApp\node_modules\@ngtools\webpack\src\ivy\index.js'
Require stack:
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\ProgressPlugin.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-webpack\src\webpack\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-webpack\src\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-angular\src\dev-server\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\architect\node\node-modules-architect-host.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\architect\node\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\models\architect-command.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\commands\serve-impl.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\schematics\tools\export-ref.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\schematics\tools\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\utilities\json-schema.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\models\command-runner.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\lib\cli\index.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\lib\init.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\bin\ng
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:92:18)
at F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\ProgressPlugin.js:412:9
at Hook.eval [as call] (eval at create (F:\#Development\Files\angularProjects\firstApp\node_modules\tapable\lib\HookCodeFactory.js:19:10), :7:1)
at NormalModule.doBuild (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:768:24)
at NormalModule.build (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:920:15)
at F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\Compilation.js:1322:12
at NormalModule.needBuild (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:1192:32)
../../../../#Development/Files/angularProjects/firstApp/src/styles.css - Error: Module build failed: Error: Cannot find module 'F:\#Development\Files\angularProjects\firstApp\node_modules\mini-css-extract-plugin\dist\loader.js'
Require stack:
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\ProgressPlugin.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-webpack\src\webpack\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-webpack\src\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-angular\src\dev-server\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\architect\node\node-modules-architect-host.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\architect\node\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\models\architect-command.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\commands\serve-impl.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\schematics\tools\export-ref.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\schematics\tools\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\utilities\json-schema.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\models\command-runner.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\lib\cli\index.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\lib\init.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\bin\ng
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:92:18)
at F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\ProgressPlugin.js:412:9
at Hook.eval [as call] (eval at create (F:\#Development\Files\angularProjects\firstApp\node_modules\tapable\lib\HookCodeFactory.js:19:10), :7:1)
at Hook.CALL_DELEGATE [as _call] (F:\#Development\Files\angularProjects\firstApp\node_modules\tapable\lib\Hook.js:14:14)
at NormalModule.doBuild (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:768:24)
at NormalModule.build (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:920:15)
at F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\Compilation.js:1322:12
../../../../#Development/Files/angularProjects/firstApp/src/app/app.component.css - Error: Module build failed (from ../../../../#Development/Files/angularProjects/firstApp/node_modules/postcss-loader/dist/cjs.js):
Error: Cannot find module 'F:\#Development\Files\angularProjects\firstApp\node_modules\postcss-loader\dist\cjs.js'
Require stack:
- F:\#Development\Files\angularProjects\firstApp\node_modules\loader-runner\lib\loadLoader.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\loader-runner\lib\LoaderRunner.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModuleFactory.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\Compiler.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\ProgressPlugin.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-webpack\src\webpack\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-webpack\src\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\build-angular\src\dev-server\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\architect\node\node-modules-architect-host.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\architect\node\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\models\architect-command.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\commands\serve-impl.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\schematics\tools\export-ref.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular-devkit\schematics\tools\index.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\utilities\json-schema.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\models\command-runner.js
- F:\#Development\Files\angularProjects\firstApp\node_modules\@angular\cli\lib\cli\index.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\lib\init.js
- C:\Users\Admin\AppData\Roaming\npm\node_modules\@angular\cli\bin\ng
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:92:18)
at loadLoader (F:\#Development\Files\angularProjects\firstApp\node_modules\loader-runner\lib\loadLoader.js:19:17)
at iteratePitchingLoaders (F:\#Development\Files\angularProjects\firstApp\node_modules\loader-runner\lib\LoaderRunner.js:182:2)
at runLoaders (F:\#Development\Files\angularProjects\firstApp\node_modules\loader-runner\lib\LoaderRunner.js:397:2)
at NormalModule.doBuild (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:773:3)
at NormalModule.build (F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\NormalModule.js:920:15)
at F:\#Development\Files\angularProjects\firstApp\node_modules\webpack\lib\Compilation.js:1322:12
Error: Module not found: Error: Can't resolve 'F:\#Development\Files\angularProjects\firstApp\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:0&sockPath=/sockjs-node' in 'F:\#Development\Files\angularProjects\firstApp'
Error: Module not found: Error: Can't resolve 'F:\#Development\Files\angularProjects\firstApp\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:0&sockPath=/sockjs-node' in 'F:\#Development\Files\angularProjects\firstApp'
Error: Module not found: Error: Can't resolve 'F:\#Development\Files\angularProjects\firstApp\node_modules\webpack-dev-server\client\index.js?http://0.0.0.0:0&sockPath=/sockjs-node' in 'F:\#Development\Files\angularProjects\firstApp'
Error: node_modules/@angular/platform-browser/platform-browser.d.ts:45:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.
This likely means that the library (@angular/platform-browser) which declares BrowserModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.
45 export declare class BrowserModule {
I have tried the following approaches to fix this issue,
- Tried deleting node_modules, deleted packacge-lock, cleared npm cache, and then finally npm installed, This approach has worked on many previous stack-overflow problems however for me the problem still persists.
- I have tried installing different versions of angular-cli, tried to match their compatibility with different node versions and different npm versions, that however I wasn't able to do properly because of multiple broken dependencies.
Please suggest some solutions, thank you
ANSWER
Answered 2021-Sep-10 at 07:17Try to install those modules separately npm install
:
npm i @angular-devkit/build-angular
npm i @ngtools/webpack
npm i mini-css-extract-plugin
npm i postcss-loader
QUESTION
I've installed tailwind using npm install tailwindcss
I then create my src/style.css file and include
`@tailwind base;`
`@tailwind components;`
`@tailwind utilities;`
When I run my build-css command I get a generated output.css file, but the file is only 425 lines long. It looks likes it's missing the components and the utilities. When I link my HTML to the output.css I get the base tailwind css styles applied, but utilities have absolutely no effect. I have followed the docs to the best of my ability as well as several tutorials with the same result every time. No clue what I am I doing wrong, the tuts I have watched show this file to be thousands of lines of code while mine is always 425.
ANSWER
Answered 2021-Dec-25 at 20:47You need to add a config js file for the tailwind engine, inside the config file use content
attribute to define where is your HTML or JS files, the new engine automatically looks inside these files and compiles only the classes that you used.
Check this video for more information:https://youtu.be/mSC6GwizOag?t=22
QUESTION
I am testing a library like follows:
std::chrono::system_clock::time_point FromDateTime(const DateTime& dateTime)
{
std::tm tm{};
tm.tm_year = dateTime.Year - 1900;
tm.tm_mon = dateTime.Month - 1;
tm.tm_mday = dateTime.Day;
tm.tm_hour = dateTime.Hour;
tm.tm_min = dateTime.Minute;
tm.tm_sec = dateTime.Second;
const auto& time = std::mktime(&tm);
const auto& timePoint = std::chrono::system_clock::from_time_t(time);
return timePoint;
}
TEST_F(MyLibraryFixture, GetDateTime)
{
// Arrange
const auto& now = std::chrono::system_clock::now();
// Act
const auto& actual = _testee->GetDateTime();
// Assert
const auto& timeDiscrepanceInSec = std::chrono::duration_cast(FromDateTime(actual) - now);
ASSERT_TRUE(timeDiscrepanceInSec.count() < 10);
}
The DateTime
type is just a raw struct with the above used fields. The call
_testee->GetDateTime();
gives a DateTime
struct back and the date time is actually local time. For some reason inherent to the library I am testing, I need to compare the local time with the time it is now. My code above seems to be working fine, I "hope" it will still work when we get back to Summer time.
Now, c++20 exposes a lot of date time utilities. I have browsed the documentation, I have tried some stuff, but I was not able to come up with a reliable counterpart to the above snippet. Is it any possible (I mean, without using std::mktime
and the strange std::tm
)?
The closest I was able to come is this, but it is still wrong (I get a discrepancy of one hour):
std::chrono::time_point FromDateTime(const DateTime& dateTime)
{
const auto& d = std::chrono::year_month_day(std::chrono::year(dateTime.Year), std::chrono::month(dateTime.Month), std::chrono::day(dateTime.Day));
const auto& t = std::chrono::hours(dateTime.Hour) + std::chrono::minutes(dateTime.Minute) + std::chrono::seconds(dateTime.Second);
const auto& dt = std::chrono::local_days(d) + t;
return dt;
}
TEST_F(MyLibraryFixture, GetDateTime)
{
// Arrange
const auto& now = std::chrono::utc_clock::now();
// Act
const auto& actual = _testee->GetDateTime();
// Assert
const auto& timeDiscrepanceInSec = std::chrono::duration_cast(FromDateTime(actual).time_since_epoch() - now.time_since_epoch());
ASSERT_TRUE(timeDiscrepanceInSec.count() < 10);
}
ANSWER
Answered 2022-Jan-20 at 14:01Here's the equivalent C++20 code to your first version of FromDateTime
:
std::chrono::system_clock::time_point
FromDateTime(const DateTime& dateTime)
{
using namespace std::chrono;
auto local_tp = local_days{year{dateTime.Year}/dateTime.Month/dateTime.Day} +
hours{dateTime.Hour} + minutes{dateTime.Minute} + seconds{dateTime.Second};
zoned_time zt{current_zone(), local_tp};
return zt.get_sys_time();
}
You were on the right track with creating a local_time
using local_days
.
There's no need to explicitly name the year_month_day
type. This is generated for you using the /
notation.
Once you have the local time, you can associate it with your computer's local time zone by constructing a zoned_time
with current_zone()
and the local_time
.
Then you can extract the sys_time
out of the zoned_time
. The sys_time
is a time_point
(seconds-precision system_clock::time_point
), which is UTC (excluding leap seconds). And this implicitly converts to the return type: system_clock::time_point
.
If desired, you could interpret the local_time
with respect to some other time zone, rather than your computer's local time zone. For example:
zoned_time zt{"America/New_York", local_tp};
In general, zoned_time
is a convenience type used to translate between local_time
and sys_time
.
QUESTION
I'm looking for ways to count the number of trailing newlines from possibly binary data either:
- read from standard input
- or already in a shell variable (then of course the "binary" excludes at least 0x0) using POSIX or coreutils utilities or maybe Perl.
This should work without temporary files or FIFOs.
When the input is in a shell variable, I already have the following (possibly ugly but) working solution:
original_string=$'abc\n\n\def\n\n\n'
string_without_trailing_newlines="$( printf '%s' "${original_string}" )"
printf '%s' $(( ${#original_string}-${#string_without_trailing_newlines} ))
which gives 3
in the above example.
The idea above is simply to subtract the string lengths and use the "feature" of command substitution that it discards any trailing newlines.
Test-Cases:printf '' | function results in: 0
printf '\n' | function results in: 1
printf '\n\n' | function results in: 2
printf '\n\n\n' | function results in: 3
printf 'a' | function results in: 0
printf 'a\n' | function results in: 1
printf 'a\n\n' | function results in: 2
printf '\na\n\n' | function results in: 2
printf 'a\n\nb\n' | function results in: 1
For the special cases when NUL
is part of the string (which anyway just works when reading from stdin, not when giving the string in the shell via avariable), the results are undefined but should typically be either:
printf '\n\x00\n\n' | function results in: 1
printf 'a\n\n\x00\n' | function results in: 2
that is counting the new lines up to the NUL
or:
printf '\n\x00\n\n' | function results in: 2
printf 'a\n\n\x00\n' | function results in: 1
that is counting the newlines from the NUL
or:
printf '\n\x00\n\n' | function results in: 3
printf 'a\n\n\x00\n' | function results in: 3
that is ignoring any "trailing" NUL
, as long as these are right before, within or right after the trailing NUL
s
or:
giving an error
ANSWER
Answered 2022-Jan-18 at 13:29Using GNU awk for RT
and without reading all of the input into memory at once:
$ printf 'abc\n\n\def\n\n\n' | awk '/./{n=NR} END{print NR-n+(n && (RT==RS))}'
3
$ printf 'a\n' | awk '/./{n=NR} END{print NR-n+(n && (RT==RS))}'
1
$ printf 'a' | awk '/./{n=NR} END{print NR-n+(n && (RT==RS))}'
0
$ printf '' | awk '/./{n=NR} END{print NR-n+(n && (RT==RS))}'
0
$ printf '\n' | awk '/./{n=NR} END{print NR-n+(n && (RT==RS))}'
1
$ printf '\n\n' | awk '/./{n=NR} END{print NR-n+(n && (RT==RS))}'
2
QUESTION
I want to create dark mode for a web site which use bootstrap. I have to add new root class which includes all boostrap colors. Here is my colors.scss:
$primary:#065FC6;
$secondary:#263C5C;
$success:#49C96D;
$danger:#FD7972;
$warning:#FF965D;
$light:#F8F8F8;
$body-color: #263C5C;
$custom-colors: (
"brd-default": $body-color
);
I want create new class like this:
:root.dark{
// override colors and classes for dark mode
$primary:#012345;
$secondary:#111111;
$success:#222222;
}
So how can i copy and paste all bootstrap colors for new color scheme?
If i can add colors, i will change HTML class so my root(color scheme) will be:
in my styles.scss:
@import "./colors";// custom colors
@import "bootstrap/scss/functions";
@import "bootstrap/scss/variables";
@import "bootstrap/scss/utilities";
ANSWER
Answered 2021-Aug-07 at 20:32As explained here, there's no way to attach a class to :root
. However, you don't need this to achieve what you want.
Simply make a dark
class then you can add that as desired to the html or body tag.
Make all the needed theme color changes inside .dark{}, and then @import "bootstrap". When .dark
doesn't exist on the body, the theme colors will return to Bootstrap defaults.
@import "functions";
@import "variables";
@import "mixins";
.dark {
/* redefine theme colors for dark theme */
$primary: #012345;
$secondary: #111111;
$success: #222222;
$dark: #000;
$theme-colors: (
"primary": $primary,
"secondary": $secondary,
"success": $success,
"danger": $danger,
"info": $indigo,
"dark": $dark,
"light": $light,
);
/* redefine theme color variables */
@each $color, $value in $theme-colors {
--#{$variable-prefix}#{$color}: #{$value};
}
/* redefine theme color rgb vars (used for bg- colors) */
$theme-colors-rgb: map-loop($theme-colors, to-rgb, "$value");
@each $color, $value in $theme-colors-rgb {
--#{$variable-prefix}#{$color}-rgb: #{$value};
}
$body-color: #eeeeee;
$body-bg: #263C5C;
--#{$variable-prefix}body-color: #{$body-color};
--#{$variable-prefix}body-bg: #{$body-bg};
@import "bootstrap";
}
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install javafx-jpa-crud
You can use javafx-jpa-crud like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the javafx-jpa-crud component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Support
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesExplore Kits - Develop, implement, customize Projects, Custom Functions and Applications with kandi kits
Save this library and start creating your kit
Share this Page